<HTML>
<HEAD>
<TITLE>Re: [APBeta] Observation attempted but not found</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>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.<BR>
<BR>
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.<BR>
<BR>
Steve<BR>
<BR>
<BR>
On 7/6/09 4:10 AM, "Jeff Young" <<a href="jey@adobe.com">jey@adobe.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT COLOR="#1F497D"><FONT SIZE="2"><FONT FACE="Arial"><SPAN STYLE='font-size:10pt'>I have also struggled with what to do about these.<BR>
<BR>
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.<BR>
<BR>
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.<BR>
<BR>
Using a separate rating (as Dan suggested) would probably work a little bit better, but as Dan said, it has issues too.<BR>
<BR>
-- Jeff.<BR>
<BR>
<BR>
</SPAN></FONT></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
</SPAN></FONT><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'><B>From:</B> <a href="apbeta-bounces@lists.astroplanner.net">apbeta-bounces@lists.astroplanner.net</a> [<a href="mailto:apbeta-bounces@lists.astroplanner.net">mailto:apbeta-bounces@lists.astroplanner.net</a>] <B>On Behalf Of </B>Paul Kemp<BR>
<B>Sent:</B> Monday, July 06, 2009 6:29 AM<BR>
<B>To:</B> AstroPlanner Beta Testers<BR>
<B>Subject:</B> Re: [APBeta] Observation attempted but not found<BR>
</SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
If I do not find an object, I do not log it.<BR>
<BR>
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.<BR>
<BR>
However, I can see this getting more and more complicated.<BR>
<BR>
So, back to square one. Just don't log it.<BR>
<BR>
Paul Kemp<BR>
13.1" f5 Reflector with Argo Navis & Paracorr<BR>
Auckland, New Zealand<BR>
36° 55' 09" South, 174° 43' 30" East<BR>
<BR>
--- The Southern Sentinel ---<BR>
www.southernsentinel.co.nz <<a href="http://www.southernsentinel.co.nz">http://www.southernsentinel.co.nz</a>> <BR>
<BR>
Checkout my Twitter: twitter.com/pulinski <<a href="http://twitter.com/pulinski">http://twitter.com/pulinski</a>> <BR>
<BR>
On Mon, Jul 6, 2009 at 5:14 PM, Michael Portuesi <<a href="portuesi@jotabout.com">portuesi@jotabout.com</a>> wrote:<BR>
</SPAN></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
</SPAN></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'><BR>
On Jul 5, 2009, at 9:02 PM, Paul Rodman wrote:<BR>
<BR>
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.<BR>
<BR>
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.<BR>
<BR>
I also think a "not found" feature for observations is a good idea.<BR>
<BR>
Michael P.<BR>
</SPAN></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
</SPAN></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'><BR>
_______________________________________________<BR>
APBeta mailing list<BR>
<a href="APBeta@lists.astroplanner.net">APBeta@lists.astroplanner.net</a><BR>
<a href="http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net">http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net</a><BR>
<BR>
</SPAN></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
<HR ALIGN=CENTER SIZE="3" WIDTH="95%"></SPAN></FONT><FONT SIZE="2"><FONT FACE="Consolas, Courier New, Courier"><SPAN STYLE='font-size:10pt'>_______________________________________________<BR>
APBeta mailing list<BR>
<a href="APBeta@lists.astroplanner.net">APBeta@lists.astroplanner.net</a><BR>
<a href="http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net">http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net</a><BR>
</SPAN></FONT></FONT></BLOCKQUOTE>
</BODY>
</HTML>