Poll: How do you enter all of your acuisition details when captured across multiple nights? AstroBin Platform open discussions community forum · Chris White- Overcast Observatory · ... · 34 · 466 · 0

This topic contains a poll.
How do you enter target acquisition details when presenting a target shot over multiple nights?
I lump all my data into one single acquisition date.
I enter all the dates in separately with their respective capture information.
I dont enter acquisition details or I just type them up in the target description.
Overcast_Observatory 19.90
...
· 
·  1 like
·  Share link
If you take data across multiple nights, do you enter all of the separate sessions in the data acquisition or just pick a single date and put your data totals?  

I don't fill out info for each session.  I have data across a dozen or more nights for a target and don't have the patience to enter them separately.  I realize this skews information about the target acquisition such as moon phase, etc…but it would be overwhelming to manage this information.  

Curious what other people do, and if there might be room for a feature that would allow you to select all the dates for the data on one single session so there was some additional information in there about the capture plan.  As it stands now, my last image had over 80 hours, all taken on a single day.  :-)
Like
darkmattersastro 11.95
...
· 
·  1 like
·  Share link
The date isn’t required so I just put the filter information in and leave the date blank.
Like
robert.zibreg 1.20
...
· 
·  Share link
You can generate csv from your data and upload that csv. Here check this out https://github.com/SteveGreaves/AstroBinUploader There's even a thread here on the forums
Edited ...
Like
Overcast_Observatory 19.90
Topic starter
...
· 
·  1 like
·  Share link
Robert Žibreg:
You can generate csv from your data and upload that csv. Here check this out https://github.com/SteveGreaves/AstroBinUploader There's even a thread here on the forums



Thanks, I for one don't make it a habit to download command line scripts off the internet. This is more of a native use of astrobon query.
Like
Vroobel
...
· 
·  1 like
·  Share link
Hi,

The more information provided the easier is others' work in estimating their chances of making their image of the object. Limited horizon, season, hours of darkness, local climate (clouds) - these factors and I think much more limit us, so I don't like when imagers are stingy or sloppy in providing useful information. Sometimes I think they do it intentionally.
Like
darkmattersastro 11.95
...
· 
·  Share link
Hi,

The more information provided the easier is others' work in estimating their chances of making their image of the object. Limited horizon, season, hours of darkness, local climate (clouds) - these factors and I think much more limit us, so I don't like when imagers are stingy or sloppy in providing useful information. Sometimes I think they do it intentionally.



Telescopius is great for this type of planning work.
Like
robert.zibreg 1.20
...
· 
·  1 like
·  Share link
Chris White- Overcast Observatory:
Robert Žibreg:
You can generate csv from your data and upload that csv. Here check this out https://github.com/SteveGreaves/AstroBinUploader There's even a thread here on the forums



Thanks, I for one don't make it a habit to download command line scripts off the internet. This is more of a native use of astrobon query.

It's a fair advice and I fully support it! (I'm also a software dev)
Like
DaveB 2.11
...
· 
·  2 likes
·  Share link
None of the above…

I typically enter a separate date for each filter to at least give an idea that the acquisition was taken across multiple nights. The dates that I enter are dates that I did acquire images, not made-up dates. And the total acquisition times per filter are accurate. But I rotate filters every night, and for me, it isn't worth the effort to enter each data set separately (e.g., 7 filters over 8 nights = 56 separate sets of data).

I do have it in my head that I might right a little script that takes advantage of the ABin API, in which case I could enter all of them separately, but I'm too busy for that right now.
Edited ...
Like
Overcast_Observatory 19.90
Topic starter
...
· 
·  2 likes
·  Share link
these factors and I think much more limit us, so I don't like when imagers are stingy or sloppy in providing useful information. Sometimes I think they do it intentionally.




No one should be obligated to take sometimes considerable amounts of time to provide this kind of information freely for other people's entitlement.    Whether people post something or nothing accompanying an image is entirely up to the person making the post.  Most people have other things in life competing with their limited time, so a system that makes it easier or more efficient is more likely to have higher rates of participation. 

This is not saying that the astrobin system for acquisition details is bad.  As it stands it allows people to go into as much or little detail as they want to.  If it was a hard requirement on astrobin to fill out all the session details that went into an image I suspect that far fewer images would be shared.  I would hazard a guess that this is why it is optional.
Like
Overcast_Observatory 19.90
Topic starter
...
· 
·  1 like
·  Share link
Dave B:
None of the above...

I typically enter a separate date for each filter to at least give an idea that the acquisition was taken across multiple nights. The dates that I enter are dates that I did acquire images, not made-up dates. And the total acquisition times per filter are accurate. But I rotate filters every night, and for me, it isn't worth the effort to enter each data set separately (e.g., 7 filters over 8 nights = 56 separate sets of data).

I do have it in my head that I might right a little script that takes advantage of the ABin API, in which case I could enter all of them separately, but I'm too busy for that right now.



This is somewhat of a new consideration for me.  When I imaged from my backyard I'd have maybe two nights on a target.  Now that I am remote I can have 20 nights on a target easily... and I can have multiple targets going at a time where a target could conceivably have a few months of data contribution.
Like
Vroobel
...
· 
·  Share link
Do you want to say that providing the detailed info consumes a comparable time to the acquisition and processing in total? Plesase…
Like
Overcast_Observatory 19.90
Topic starter
...
· 
·  1 like
·  Share link
Do you want to say that providing the detailed info consumes a comparable time to the acquisition and processing in total? Plesase...



I see... you are arguing about something that I didn't say...

I'm saying, that entering all the individual session details is not worth my time.... YMMV.
Like
darkmattersastro 11.95
...
· 
·  Share link
Do you want to say that providing the detailed info consumes a comparable time to the acquisition and processing in total? Plesase...



I didn’t see this claim be made here by anyone.
Like
EsaViitala 1.20
...
· 
·  Share link
Recently I’ve begun entering the start date for each session, if a session spans over two dates (over midnight), as it often does, all my frames from that night sort under that start date.
Like
Vroobel
...
· 
·  2 likes
·  Share link
Chris White- Overcast Observatory (Overcast_Observatory)

...Most people have other things in life competing with their limited time...

It takes me less than 10 minutes each time which is NOTHING in comparison to e.g. 27h of imaging + processing and post-processing. This is how I understand it.

I don't want to argue, it's not my goal. The world would be better if we could be more helpful to others.
Edited ...
Like
CCDnOES 8.34
...
· 
·  2 likes
·  Share link
IMHO it is polite to enter the exposure details for each filter (exposure time, binning, maybe gain and filter type). Also scope aperture/speed/type). It can help others imaging that target.

As far as dates, that really does not matter so I tend to just make a note in the description that I took the images over "X" nights between date "Y" and date "Z". It is way too much effort to enter these by each night imaged and benefits no one.
Edited ...
Like
Overcast_Observatory 19.90
Topic starter
...
· 
·  2 likes
·  Share link
Bill McLaughlin:
IMHO it is polite to enter the exposure details for each filter (exposure time, binning, maybe gain and filter type). Also scope aperture/speed/type). It can help others imaging that target.

As far as dates, that really does not matter so I tend to just make a note in the description that I took the images over "X" nights between date "Y" and date "Z". It is way too much effort to enter these by each night imaged and benefits no one.



Yes, i agree.  How much integration time for each channel is important.
Like
starry_night_observer 3.01
...
· 
·  2 likes
·  Share link
For this topic I can see both sides of the issue. Where an individual has numerous nights data with various pieces of kit, it can be time consuming to input all the data, and some people are very busy with other aspects of their lives, job, family and such, but this is a time consuming hobby in the first place as most hobbies are. Being verily new to the hobby I appreciate the info. Personally I use astrobin as a resource of valuable information in acquiring my images. The info gives me an idea as to whether I can image an object or is it best left to another time when I have better equipment, and if I do image an object with similar equipment, what I can reasonably expect. Also I use it to see what others have done in their editing process so I can see what a good edit looks like. As far as the acquiring detail is concerned, just knowing how long the integration is and if filters where used is enough for me. One piece of info that a lot of people forget to include in their description and I find extremely useful is the bortle of the area the image was acquired at. What takes 5hrs in a Bortle 3 sky might take me 15 or more hours in my Bortle 6 sky to achieve a similar result. I find this info more important that all the dates and times. Why I try to include this info in every image I post. I tend to separate my acquisition info, but at best I’m only shooting 2 maybe 3 nights, and I’m retired and have nothing but time. So that’s my take. To sum it up, for me, a total time, if filters where used, and the Bortle of your area.
Like
andreatax 9.89
...
· 
·  2 likes
·  Share link
Anything and everything should really be entered, down to the date (which needs to be there to calculate the average moon phase if nothing else), seeing and Bortle scale and not only across several night but several night over several years. If I had an automate weather station it would be nice to enter external temperatures (and many other things besides). Number of Flat/Bias/Darks are totally pointless. I did this book-keeping for the past 20 odd years and I can't see changing it now.
Like
AccidentalAstronomers 18.64
...
· 
·  2 likes
·  Share link
Robert Žibreg:
You can generate csv from your data and upload that csv. Here check this out https://github.com/SteveGreaves/AstroBinUploader There's even a thread here on the forums

I've been meticulous about recording every stat I possibly can completely and accurately since I started here almost five years ago. I hate doing it, but I wanted that data recorded primarily for my own use. It has been a monumental hassle and has made me dread uploading each and every new image. And in the last year, since I installed my remote scopes and have extended my project times, it has really been horrible. Sal has made it better over the years, but it's still pretty awful to deal with. That's not Salvatore's fault, it's just the nature of the beast. 

Today, based on your post, I installed the script. It was a bit of a pain to get configured and working right, but this is literally life-changing for me. What used to take me an hour--or twice that long on large mosaics or 100+ hour projects spanning many nights--now takes 2 minutes. Thank you so much, Robert! I owe you a beer--probably a case of beer. Hell, if you like scotch, I'll buy you a MacAllan 25.
Edited ...
Like
robert.zibreg 1.20
...
· 
·  1 like
·  Share link
Timothy Martin:
Robert Žibreg:
You can generate csv from your data and upload that csv. Here check this out https://github.com/SteveGreaves/AstroBinUploader There's even a thread here on the forums

I've been meticulous about recording every stat I possibly can completely and accurately since I started here almost five years ago. I hate doing it, but I wanted that data recorded primarily for my own use. It has been a monumental hassle and has made me dread uploading each and every new image. And in the last year, since I installed my remote scopes and have extended my project times, it has really been horrible. Sal has made it better over the years, but it's still pretty awful to deal with. That's not Salvatore's fault, it's just the nature of the beast. 

Today, based on your post, I installed the script. It was a bit of a pain to get configured and working right, but this is literally life-changing for me. What used to take me an hour--or twice that long on large mosaics or 100+ hour projects spanning many nights--now takes 2 minutes. Thank you so much, Robert! I owe you a beer--probably a case of beer. Hell, if you like scotch, I'll buy you a MacAllan 25.

I feel that pain as well, this python script made my day. I'm a beer man btw.
Like
rveregin 8.47
...
· 
·  3 likes
·  Share link
Personally, for my own data I always enter by date, but my situation is not complex, I image with one filter on one night. Note though, it is very easy for multiple nights to copy information from one night to the next, so one only for example needs to change number of exposures, or seeing from night to night on the same target. 

If I am processing data from elsewhere, and filters change every night, over many nights, there is no way I would try to put all that in. So I would just summarize the info for each filter for example, and maybe a comment if there was any issue with any nights or filters. Life is too short to require every detail…

So in the end, it really is about how much effort is involved, we must respect everyone's time. And note it is not fair to equate integration time, which really matters, with time to fill in forms. I'm super happy with anyone who takes the time to put in the critical information, whether in the forms or added in the description. Though obviously for some things using the forms helps a lot with searches. 

But details on every night is information that is not that critical, as long as the information provide on captures is accurate.

I do admit it annoys me when there is no equipment or acquisition information at all, it takes less than a minute to do that. It is just impossible to judge an image without some key information.
CS everyone
Rick
Like
DalePenkala 19.38
...
· 
·  3 likes
·  Share link
Hello Chris,
I always put in the dates and info as much as I can on my images. Maybe the exception would be if I’m doing simple DSLR work on a tripod or something but for my images that I capture with either of my rigs the dates and information is input into the AB platform. From my perspective were all here to share our knowledge and images so thats what I do anyway. I’m not as knowledgeable as may are here but I share what I can while I’m on here.
I’ve not taken 80hrs of data yet but in the 60hr range and yes for me I input all the dates. I have all that info already when I process my data so for an extra couple of minutes I add it to the image info. I know when I’m looking at others images to see if its something within my reach that info helps me to determine if I’m able to get it or not.

Dale
Like
Overcast_Observatory 19.90
Topic starter
...
· 
·  1 like
·  Share link
Dale Penkala:
Hello Chris,
I always put in the dates and info as much as I can on my images. Maybe the exception would be if I’m doing simple DSLR work on a tripod or something but for my images that I capture with either of my rigs the dates and information is input into the AB platform. From my perspective were all here to share our knowledge and images so thats what I do anyway. I’m not as knowledgeable as may are here but I share what I can while I’m on here.
I’ve not taken 80hrs of data yet but in the 60hr range and yes for me I input all the dates. I have all that info already when I process my data so for an extra couple of minutes I add it to the image info. I know when I’m looking at others images to see if its something within my reach that info helps me to determine if I’m able to get it or not.

Dale



Thanks Dale.   What is important to you as a spectator?  For people to have all the dates and data input for each one... or just to know how many subs and exposure length in each channel?
Like
DalePenkala 19.38
...
· 
·  2 likes
·  Share link
Chris White- Overcast Observatory:
Dale Penkala:
Hello Chris,
I always put in the dates and info as much as I can on my images. Maybe the exception would be if I’m doing simple DSLR work on a tripod or something but for my images that I capture with either of my rigs the dates and information is input into the AB platform. From my perspective were all here to share our knowledge and images so thats what I do anyway. I’m not as knowledgeable as may are here but I share what I can while I’m on here.
I’ve not taken 80hrs of data yet but in the 60hr range and yes for me I input all the dates. I have all that info already when I process my data so for an extra couple of minutes I add it to the image info. I know when I’m looking at others images to see if its something within my reach that info helps me to determine if I’m able to get it or not.

Dale



Thanks Dale.   What is important to you as a spectator?  For people to have all the dates and data input for each one... or just to know how many subs and exposure length in each channel?

In all honesty the latter would be most beneficial to me, however if there is something specific to the data collection then I always read the description.
I was just adding my 2 cents as to how I input my data is all. I thought that might be helpful to your post here is all.

Dale
Like
 
Register or login to create to post a reply.