[APBeta] Observation attempted but not found

[Jeff Young]

Paul --

I assume that the new field defaults to "on" so that we can ignore it 95% of the time?  (In other words, we only have to uncheck "observed" in the few cases where we couldn't find anything.)

-- Jeff.


> -----Original Message-----
> From: apbeta-bounces at lists.astroplanner.net [mailto:apbeta-bounces at lists.astroplanner.net] On Behalf Of
> Paul Rodman
> Sent: Monday, July 06, 2009 9:22 PM
> To: AstroPlanner Beta Testers
> Subject: Re: [APBeta] Observation attempted but not found
> 
> 
> On Jul 6, 2009, at 9:28 AM, Paul Rodman wrote:
> 
> >
> > On Jul 6, 2009, at 6:54 AM, Paul Rodman wrote:
> >
> >> Well, what I would probably do is add another column to the
> >> Telescope/Eyepiece/.../Rating list called "Observed" with a
> >> checkbox in it (initially ON). Thus you'd be able to record that an
> >> object was not observed with such-and-such a combination, but was
> >> observed with, say, a shorter FL eyepiece. That would be relatively
> >> easy to implement.
> >>
> >> What would be trickier would be to display # of observations to
> >> include only those that have at least one "observed" entry.
> >>
> >> Let me ponder this.
> 
> OK, this is now implemented (including highlighting and observation
> rules, scripting, etc.) as an Observed field in the resource
> combinations list. If one or more of those entries are marked as
> Observed, the the observation is considered "Observed" (i.e. you were
> able to see the object with at least one combination of telescope,
> eyepiece, etc.).
> 
> However, an observation is still an observation (whether the object
> was "observed" or not). Hence, the number of observations remains the
> same.
> 
> Perhaps we can debate changing "Observed" to "Detected", "Seen", etc.
> 
> Paul R.
> 
> _______________________________________________
> APBeta mailing list
> APBeta at lists.astroplanner.net
> http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net