<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Vrinda;
panose-1:1 1 6 0 1 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"Trebuchet MS";
panose-1:2 11 6 3 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Tekst zonder opmaak Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Ballontekst Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.E-mailStijl17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.TekstzonderopmaakChar
{mso-style-name:"Tekst zonder opmaak Char";
mso-style-priority:99;
mso-style-link:"Tekst zonder opmaak";
font-family:Consolas;}
span.BallontekstChar
{mso-style-name:"Ballontekst Char";
mso-style-priority:99;
mso-style-link:Ballontekst;
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="2050" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=NL link=blue vlink=purple>
<div class=Section1>
<p class=MsoPlainText><span lang=EN-US>Hi folks,<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>I'm the requester. I logged over 5000
observations in AP already and I more than ever feel the need to log many details,
both of the object and the environmentals.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>My reasoning is that values such as
seeing, transparency and SQM (sky quality, a measurement for darkness) are of
great importance to an observation. Seeing and transparency change during an
observing session. So does SQM, to an even greater extent. My Unihedron Sky
Quality Meter also measures temperature, which I also log (although not
directly of influence to an objects visibility). These variables together
create a database I find more than a little useful. Thanks to AP and these
logged values I can instantly recall the conditions under which an object was
visible. To me it’s invaluable.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>While a general value for seeing, transparency
and SQM is acceptable for a session I definitely won’t stop to log these
details separately for an observed object. Currently AP allows plenty of user
fields to be added to an observation, so the option is there. However, these
values are not repeated for the next observations logged in a session, requiring
them to be entered manually again and again. It would have my great preference
to see AP have the option to fill in a value for a user field which would then
be duplicated for the next observation (of a different object), until the value
changes, after which the new value will be used for subsequent observations. Actually,
I could live without fields for seeing & transparency for the session, as I
could enter this in a brief description of the session itself.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>In the field I have often noticed seeing
is different for different parts of the sky. Hence my desire to enter different
values during a session. Same goes for transparency, light pollution or Lunar
interference. What about winds that shake your scope early in the session but die
down later at night, allowing stable views and easier split double stars?<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>All of that and a new SQM reading
roughly every fifteen minutes. That’s why I put in the request.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>Best wishes to all,<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Trebuchet MS","sans-serif";
color:#1F497D'> </span><b><span lang=EN-US style='font-family:"Trebuchet MS","sans-serif";
color:black'>Victor van Wulfen<o:p></o:p></span></b></p>
<p class=MsoNormal><b><span lang=EN-US style='font-size:4.0pt;font-family:"Trebuchet MS","sans-serif";
color:black'><o:p> </o:p></span></b></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><img width=240 height=102 id="Afbeelding_x0020_1"
src="cid:image001.jpg@01CA17B5.EDA16FE0" alt=Handtekening></span><span
lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><b><span lang=EN-US style='font-size:9.0pt;font-family:"Trebuchet MS","sans-serif";
color:black'> </span></b><span lang=EN-US style='font-size:9.0pt;font-family:
"Trebuchet MS","sans-serif";color:blue'><a href="http://www.clearskies.eu/"><span
style='text-decoration:none'>www.clearskies.eu</span></a><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Van:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Paul Kemp
[mailto:paul@bluedahlia.co.nz] <br>
<b>Verzonden:</b> vrijdag 7 augustus 2009 22:04<br>
<b>Aan:</b> AstroPlanner Beta Testers<br>
<b>Onderwerp:</b> Re: [APBeta] Seeing/Transparency<o:p></o:p></span></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US>I see the
rationale for <b><u>b</u></b>, but I think that <b><u>a</u></b> is probably the
best option. Offers functionality and ease. I am starting to see APv2 getting
more complicated regarding logging observations.<br>
<br>
When I log observations 3000+, I just take the general feel for seeing over the
whole session.<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>
</span><a href="http://www.southernsentinel.co.nz"><span lang=EN-US>www.southernsentinel.co.nz</span></a><span
lang=EN-US><br>
<br>
Checkout my Twitter: </span><a href="http://twitter.com/pulinski"><span
lang=EN-US>twitter.com/pulinski</span></a><span lang=EN-US><br>
<br>
<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US>On Sat, Aug 8, 2009 at 7:36 AM, David Crum
<</span><a href="mailto:crum.david@gmail.com"><span lang=EN-US>crum.david@gmail.com</span></a><span
lang=EN-US>> wrote:<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US>I too kinda like option B, but like other
posters have already said,<br>
it's not that big a deal. </span>So, either way works :)<o:p></o:p></p>
<p class=MsoNormal><span lang=EN-US><br>
On Fri, Aug 7, 2009 at 3:29 PM, Hilary Jones<</span><a
href="mailto:hdjones@pacbell.net"><span lang=EN-US>hdjones@pacbell.net</span></a><span
lang=EN-US>> wrote:<br>
> I'll vote for b. But realistically it's not going to make a big
difference<br>
> to me either way.<br>
><br>
> Hilary<br>
><br>
> ----- Original Message ----- From: "Paul Rodman" <</span><a
href="mailto:paul@ilanga.com"><span lang=EN-US>paul@ilanga.com</span></a><span
lang=EN-US>><br>
> To: "AstroPlanner Beta Testers" <</span><a
href="mailto:apbeta@lists.astroplanner.net"><span lang=EN-US>apbeta@lists.astroplanner.net</span></a><span
lang=EN-US>><br>
> Sent: Friday, August 07, 2009 10:29 AM<br>
> Subject: [APBeta] Seeing/Transparency<br>
><br>
><br>
>> Folks,<br>
>><br>
>> A user has requested that the Seeing/Transparency be per observation*<br>
>> rather than per session, his argument being that those values change
over<br>
>> the period of an observing session. Does anyone else have strong
feelings<br>
>> about this either way?<br>
>><br>
>> As I see it (sic):<br>
>><br>
>> a. Per session: less hassle, but not so fine grained. If the seeing
(say)<br>
>> changed from bad to good over the period of the session, it
might not be<br>
>> clear as to why an observation was or wasn't successful.<br>
>><br>
>> b. Per observation: more hassle (although the default would be to make
the<br>
>> value the same as for the last observation in the session).
Session could<br>
>> display range of seeing/transparency based on its included
observations.<br>
>><br>
>> Paul R.<br>
>><br>
>> * per resource-combination within an observation might be pushing it.<br>
>><br>
>> _______________________________________________<br>
>> APBeta mailing list<br>
>> </span><a href="mailto:APBeta@lists.astroplanner.net"><span
lang=EN-US>APBeta@lists.astroplanner.net</span></a><span lang=EN-US><br>
>> </span><a
href="http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net"
target="_blank"><span lang=EN-US>http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net</span></a><span
lang=EN-US><br>
><br>
> _______________________________________________<br>
> APBeta mailing list<br>
> </span><a href="mailto:APBeta@lists.astroplanner.net"><span lang=EN-US>APBeta@lists.astroplanner.net</span></a><span
lang=EN-US><br>
> </span><a
href="http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net"
target="_blank"><span lang=EN-US>http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net</span></a><span
lang=EN-US><br>
><br>
_______________________________________________<br>
APBeta mailing list<br>
</span><a href="mailto:APBeta@lists.astroplanner.net"><span lang=EN-US>APBeta@lists.astroplanner.net</span></a><span
lang=EN-US><br>
</span><a
href="http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net"
target="_blank"><span lang=EN-US>http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net</span></a><span
lang=EN-US><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Van:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Paul Kemp
[mailto:paul@bluedahlia.co.nz] <br>
<b>Verzonden:</b> vrijdag 7 augustus 2009 22:04<br>
<b>Aan:</b> AstroPlanner Beta Testers<br>
<b>Onderwerp:</b> Re: [APBeta] Seeing/Transparency<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>I see the rationale for <b><u>b</u></b>,
but I think that <b><u>a</u></b> is probably the best option. Offers
functionality and ease. I am starting to see APv2 getting more complicated
regarding logging observations.<br>
<br>
When I log observations 3000+, I just take the general feel for seeing over the
whole session.<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>
<a href="http://www.southernsentinel.co.nz">www.southernsentinel.co.nz</a><br>
<br>
Checkout my Twitter: <a href="http://twitter.com/pulinski">twitter.com/pulinski</a><br>
<br>
<o:p></o:p></p>
<div>
<p class=MsoNormal>On Sat, Aug 8, 2009 at 7:36 AM, David Crum <<a
href="mailto:crum.david@gmail.com">crum.david@gmail.com</a>> wrote:<o:p></o:p></p>
<p class=MsoNormal>I too kinda like option B, but like other posters have
already said,<br>
it's not that big a deal. So, either way works :)<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal><br>
On Fri, Aug 7, 2009 at 3:29 PM, Hilary Jones<<a
href="mailto:hdjones@pacbell.net">hdjones@pacbell.net</a>> wrote:<br>
> I'll vote for b. But realistically it's not going to make a big difference<br>
> to me either way.<br>
><br>
> Hilary<br>
><br>
> ----- Original Message ----- From: "Paul Rodman" <<a
href="mailto:paul@ilanga.com">paul@ilanga.com</a>><br>
> To: "AstroPlanner Beta Testers" <<a
href="mailto:apbeta@lists.astroplanner.net">apbeta@lists.astroplanner.net</a>><br>
> Sent: Friday, August 07, 2009 10:29 AM<br>
> Subject: [APBeta] Seeing/Transparency<br>
><br>
><br>
>> Folks,<br>
>><br>
>> A user has requested that the Seeing/Transparency be per observation*<br>
>> rather than per session, his argument being that those values change over<br>
>> the period of an observing session. Does anyone else have strong
feelings<br>
>> about this either way?<br>
>><br>
>> As I see it (sic):<br>
>><br>
>> a. Per session: less hassle, but not so fine grained. If the seeing
(say)<br>
>> changed from bad to good over the period of the session, it
might not be<br>
>> clear as to why an observation was or wasn't successful.<br>
>><br>
>> b. Per observation: more hassle (although the default would be to make
the<br>
>> value the same as for the last observation in the session).
Session could<br>
>> display range of seeing/transparency based on its included
observations.<br>
>><br>
>> Paul R.<br>
>><br>
>> * per resource-combination within an observation might be pushing it.<br>
>><br>
>> _______________________________________________<br>
>> APBeta mailing list<br>
>> <a href="mailto:APBeta@lists.astroplanner.net">APBeta@lists.astroplanner.net</a><br>
>> <a
href="http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net"
target="_blank">http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net</a><br>
><br>
> _______________________________________________<br>
> APBeta mailing list<br>
> <a href="mailto:APBeta@lists.astroplanner.net">APBeta@lists.astroplanner.net</a><br>
> <a
href="http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net"
target="_blank">http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net</a><br>
><br>
_______________________________________________<br>
APBeta mailing list<br>
<a href="mailto:APBeta@lists.astroplanner.net">APBeta@lists.astroplanner.net</a><br>
<a href="http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net"
target="_blank">http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net</a><o:p></o:p></p>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</body>
</html>