[APBeta] Seeing/Transparency

[V.A. van Wulfen]

Yes, it would. I believe this would be the best of both worlds: A general
value for a session with specifics for an observation. Copying the user
field value from a previous observation saves a lot of time by not having to
reenter identical values every time.

 

Thanks!

 

 Victor van Wulfen

 

Handtekening

  <http://www.clearskies.eu/> www.clearskies.eu

 

 

 

Van: Paul Rodman [mailto:paul at ilanga.com] 
Verzonden: vrijdag 7 augustus 2009 23:42
Aan: AstroPlanner Beta Testers
Onderwerp: Re: [APBeta] Seeing/Transparency

 

Well, it would be much easier at this stage just to add the option to copy
over all the user field values from the previous observation in the session
when a new observation is added. This, it would seem, resolves most of your
problem/s.

 

The seeing/transparency per observation change is nasty enough to warrant
waiting for V2.1.

 

Paul R.

 

On Aug 7, 2009, at 2:22 PM, V.A. van Wulfen wrote:





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.

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.

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.

 

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?

All of that and a new SQM reading roughly every fifteen minutes. That's why
I put in the request.

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.astroplanner.net/pipermail/apbeta-astroplanner.net/attachments/20090808/815437a6/attachment-0003.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 4838 bytes
Desc: not available
URL: <http://lists.astroplanner.net/pipermail/apbeta-astroplanner.net/attachments/20090808/815437a6/attachment-0003.jpeg>