New acquisition details form available for testing AstroBin Beta Testers · Salvatore Iovene · ... · 56 · 1013 · 8

gorante 2.62
...
· 
·  1 like
Just testing now, looks easy and effective, no issues found so far.

The "copy" feature in acquisition settings alone is worth the all the work done, imho.
Like
Paul.Puntin 3.31
...
· 
·  1 like
Just used the new form today and it’s so much easier and quicker to enter data. Quite intuitive to use too. Didn’t have any problems filling in all the info that I needed to enter. The copy feature especially makes entering acquisition data a breeze. Just copy your first line, after entering the main data and hidden optional data for your first filter, then change the filter and number of exposures in the copied line. Thanks for all your hard work.
Like
siovene
...
· 
·  3 likes
Awesome! I'm quite ecstatic with receiving such positive feedback. Hopefully this time around I don't get many complaints like "why did you have to change it, it was better before! 😡"

I'm currently working on adding a load/save preset function (same as with the equipment items), then I will begin a roll out to a wider audience.
Like
frankz 3.01
...
· 
No way, it’s so much better now! Thanks for this enhancement.
Very minor UI report: the additional properties dialog, under “Mean FWHM”, reads "Mean SQM mag/arcsec^2 as measured by your Sky Quality Meter” which seems wrong.
Francesco
Like
siovene
...
· 
Francesco Meschia:
No way, it’s so much better now! Thanks for this enhancement.
Very minor UI report: the additional properties dialog, under “Mean FWHM”, reads "Mean SQM mag/arcsec^2 as measured by your Sky Quality Meter” which seems wrong.
Francesco

Thanks, a copy/paste mistake. Fix is deploying.

Did anyone test the solar system acquisition fields?
Like
r4um 0.00
...
· 
·  2 likes
Allowing this via API would be great, just parse the FITS headers in the captures, group by date and update.
Like
siovene
...
· 
·  1 like
Hi all,

I just added a button to copy acquisition sessions from another image. I tried the presets solution but it doesn’t play well with the database design and I would have had to write some not so nice code.

Please try it out at the next chance, I can’t wait to get all of this out to everyone!

Thanks 🙃
Like
dweinbrenner 2.11
...
· 
Hi Salvatore,

it seems copying over sessions does not carry over the Bortle information.
Like
siovene
...
· 
·  1 like
Dominik Weinbrenner:
Hi Salvatore,

it seems copying over sessions does not carry over the Bortle information.

This is by design, as the Bortle information is deemed to be a local condition dependent on the location and the current conditions at the moment. Having a Bortle 1 location does not guarantee that it's Bortle 1 every night of the year.
Like
frankz 3.01
...
· 
·  2 likes
Salvatore Iovene:
Dominik Weinbrenner:
Hi Salvatore,

it seems copying over sessions does not carry over the Bortle information.

This is by design, as the Bortle information is deemed to be a local condition dependent on the location and the current conditions at the moment. Having a Bortle 1 location does not guarantee that it's Bortle 1 every night of the year.

I would instead suggest that copying it over would result in less user burden for all those cases, like changing filters within a night, where the conditions are the same. And it wouldn't impose any additional burden (i.e. it would need to be edited anyway) when the sessions correspond to different nights or locations. In other words, impose the burden only where it is relevant, instead of in every case regardless of relevance.
Like
siovene
...
· 
·  1 like
Francesco Meschia:
I would instead suggest that copying it over would result in less user burden for all those cases, like changing filters within a night, where the conditions are the same. And it wouldn't impose any additional burden (i.e. it would need to be edited anyway) when the sessions correspond to different nights or locations. In other words, impose the burden only where it is relevant, instead of in every case regardless of relevance.


Hi Francesco,
I'm not sure I understand.

If you select "Copy from a different image", how could AstroBin know if conditions such as Bortle scale, seeing, temperature, etc, were the same?

As it is now, I chose not to copy those local conditions because I prefer missing information to incorrect information.

However, I could add a checkbox in the modal dialog to select the image, that says "Copy local conditions too".

How's that sound?
Like
dweinbrenner 2.11
...
· 
Salvatore Iovene:

Perfect!
Like
GalacticRAVE 5.87
...
· 
much of an improvement, and the copy option is great! entering the temperature for the camera seems to be buggy (it converts my entry (-10) into -35 ... Matthias
Like
siovene
...
· 
much of an improvement, and the copy option is great! entering the temperature for the camera seems to be buggy (it converts my entry (-10) into -35 ... Matthias

Was this user error or something else? I see your last image and the acquisitions say -10:

Screen Shot 2023-02-25 at 17.57.46.jpg
Like
GalacticRAVE 5.87
...
· 
yes, but I for every entry had to change it. First entry -10 -> check showed -35, then changed it again to -10. accepted.
Like
siovene
...
· 
yes, but I for every entry had to change it. First entry -10 -> check showed -35, then changed it again to -10. accepted.

Thanks. Was this when copying from a different image, or when copying one row?
Like
GalacticRAVE 5.87
...
· 
when copying one row
Like
siovene
...
· 
when copying one row

I cannot reproduce, and looking at the code I cannot see how that's possible. Do you remember if that "-35" was  somewhere else? In other words, did AstroBin copy the wrong field? It couldn't just make up a random number -35.
Like
frankz 3.01
...
· 
Salvatore Iovene:
Francesco Meschia:
I would instead suggest that copying it over would result in less user burden for all those cases, like changing filters within a night, where the conditions are the same. And it wouldn't impose any additional burden (i.e. it would need to be edited anyway) when the sessions correspond to different nights or locations. In other words, impose the burden only where it is relevant, instead of in every case regardless of relevance.


Hi Francesco,
I'm not sure I understand.

If you select "Copy from a different image", how could AstroBin know if conditions such as Bortle scale, seeing, temperature, etc, were the same?

As it is now, I chose not to copy those local conditions because I prefer missing information to incorrect information.

However, I could add a checkbox in the modal dialog to select the image, that says "Copy local conditions too".

How's that sound?

When I hit the copy button for one session, Astrobin *already* assumes the new session is in the same night... because the date of the session gets copied already. So the *consistent* thing to do is to assume that, for another session in the same night, the conditions are the same.
Like
siovene
...
· 
Francesco Meschia:
When I hit the copy button for one session, Astrobin *already* assumes the new session is in the same night... because the date of the session gets copied already. So the *consistent* thing to do is to assume that, for another session in the same night, the conditions are the same.


When you do "Copy from another image", AstroBin clears your current acquisition sessions on the form, and copies from another image. It has no way of knowing that the other image was acquired on the same night...

But I think the following solution should be acceptable:

Screen Shot 2023-02-25 at 18.29.06.jpg
Like
siovene
...
· 
To be clear, just in case there was a misunderstanding:

 - When you copy a single session using the copy (or duplicate) button, all data is copied, including the date and the local conditions such as Bortle scale
 - When you copy from a different image, then the default is to not copy dates and local conditions, but I'm adding checkboxes to change that if you want (e.g. when you know that the local conditions were the same as the other image)
Like
frankz 3.01
...
· 
·  1 like
Salvatore Iovene:
To be clear, just in case there was a misunderstanding:

 - When you copy a single session using the copy (or duplicate) button, all data is copied, including the date and the local conditions such as Bortle scale
 - When you copy from a different image, then the default is to not copy dates and local conditions, but I'm adding checkboxes to change that if you want (e.g. when you know that the local conditions were the same as the other image)

My bad Salvatore, I had completely misunderstood the scenario. All clear and good now, please disregard my comments.
Like
GalacticRAVE 5.87
...
· 
·  1 like
Salvatore Iovene:
when copying one row

I cannot reproduce, and looking at the code I cannot see how that's possible. Do you remember if that "-35" was  somewhere else? In other words, did AstroBin copy the wrong field? It couldn't just make up a random number -35.



I will carefully check next time/ take screenshots, so if it is a bug that may help you to track it down. Matthias
Like
-Amenophis- 1.43
...
· 
Hello everyone,

I just tested this new feature.
Very ergonomic and easy to use. I did not encounter any particular problem.

On the other hand, I always ask to integrate the acquisition details per panel when a mosaic is made.

Thomas.
Like
derekm_abin 0.00
...
· 
Salvatore Iovene:
Awesome! I'm quite ecstatic with receiving such positive feedback. Hopefully this time around I don't get many complaints like "why did you have to change it, it was better before! 😡"

I'm currently working on adding a load/save preset function (same as with the equipment items), then I will begin a roll out to a wider audience.

It sounds great Salvatore - well done!
I have just joined the beta testers group in the hopes of getting earlier access to the new acquisition details form. I have been looking forward to this for a long time for improved ease of use. I hope that it will result in more people entering their image details. I have a multi year image (2020, 2021 and 2022) that I just put together and I was not looking forward to entering the acquisition details. The total imaging time is about 44 hours and it was captured with a combination of OSC and mono (LRGB). The image itself is OK nothing spectacular. I  merged the multi year data because I have it available and just want to keep adding to it as the seasons come round again.

Regards

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