[APBeta] Observation attempted but not found

[Steve Barkes]

You could extend that thought by creating a resource for an eyepiece called
³Unable to Observe² or some such thing.  Then you could script a report for
those objects.  I too would like some way of flagging these types of objects
and I think this would work for me.

I¹m currently going through the Finest NGC list, and have had 3 observing
sessions where I can¹t honestly say that I¹ve been able to ³see² the Bubble
Nebula.  For each of those sessions I do have a log entry of what I tried,
so my feeling is that it really should show up in the observed lists, but
just as unsuccessful.

Steve


On 7/6/09 4:10 AM, "Jeff Young" <jey at adobe.com> wrote:

> I have also struggled with what to do about these.
>  
> I do want to log them, because I want to record the conditions under which I
> wasn¹t able to find it -- that way I know whether it¹s an entirely lost cause,
> or perhaps that I just need to try again under better conditions.
>  
> I was using ³no eyepiece² to encode ³not observed².  That way I know what
> telescope I tried with, but I still get some searchable indication of ³not
> observed².  However, when 17P/Holmes became naked-eye I logged a few
> observations and those now also appear with the ³not observed² ones.
>  
> Using a separate rating (as Dan suggested) would probably work a little bit
> better, but as Dan said, it has issues too.
>  
> -- Jeff.
>  
>  
> 
> From: apbeta-bounces at lists.astroplanner.net
> [mailto:apbeta-bounces at lists.astroplanner.net] On Behalf Of Paul Kemp
> Sent: Monday, July 06, 2009 6:29 AM
> To: AstroPlanner Beta Testers
> Subject: Re: [APBeta] Observation attempted but not found
>  
> If I do not find an object, I do not log it.
> 
> But I can understand that someone might want to mark something as not
> observed. The easiest way I can see that this could be implemented is to just
> mark the object as unobserved and do not count it in the number of times
> observed. The non-observed object appears in the session, but not the list of
> observations for that object.
> 
> However, I can see this getting more and more complicated.
> 
> So, back to square one. Just don't log it.
> 
> Paul Kemp
> 13.1" f5 Reflector with Argo Navis & Paracorr
> Auckland, New Zealand
> 36° 55' 09" South, 174° 43' 30" East
> 
> --- The Southern Sentinel ---
> www.southernsentinel.co.nz <http://www.southernsentinel.co.nz>
> 
> Checkout my Twitter: twitter.com/pulinski <http://twitter.com/pulinski>
> 
> On Mon, Jul 6, 2009 at 5:14 PM, Michael Portuesi <portuesi at jotabout.com>
> wrote:
> 
> 
> On Jul 5, 2009, at 9:02 PM, Paul Rodman wrote:
> 
> What about a boolean observation user-defined field called "Not found"? That
> will give you a checkbox. Unfortunately, it will be logged as an observation,
> and won't be flagged in the list of observations.
>  
> As long as there is some sort of means to select the "not found" observations
> from the others (perhaps via a script?), that would probably be a good
> stand-in for a true implementation of the feature.
> 
> I also think a "not found" feature for observations is a good idea.
> 
> Michael P.
> 
> 
> _______________________________________________
> APBeta mailing list
> APBeta at lists.astroplanner.net
> http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net
>  
> 
> 
> _______________________________________________
> APBeta mailing list
> APBeta at lists.astroplanner.net
> http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.astroplanner.net/pipermail/apbeta-astroplanner.net/attachments/20090706/9383680f/attachment-0003.htm>