1.20
#...
·
·
4
likes
|
|---|
|
Hi, I would really appreciate to see a feature for importing Acquisition details from a text file (like any predefined format of .txt, .csv, .json, you name it) Recently, I manually filled acquisition details for a relatively small artwork. This is an image with a 26-hour total exposure. A total of 137 frames in 6 filters for 10 nights. 31 items of the list that I filled in manually on web form. But I also have a material of hundreds hours, thousand subframes to process, one of the queue it that took three years, and hundreds of nights to take. And what if it is a mosaics with 7 filters are shot with interleaving frames? Few of the human beings has enough time or patience to fill out thousand lines of details properly in a web form. On the other hand, in half an hour I wrote a script that collects all required data into a text file automatically. In the future, I can make it's public version, or it will become a feature of image acquisition software. |
|
1.20
#...
·
·
1
like
|
|---|
|
There is also an issue with Acquisition Details online form itself (or filters naming convention). You can't see the difference in the truncated filter names. I'd misselected a filter in one line and had to open dropdowns on each line to find the mistake.  |
 #...
·
·
2
likes
|
|---|
|
Hi Igor, thanks for the request. The issue with not displaying the entire filter name is now solved, and work for a CSV importer is in progress! Best regards, Salvatore |
#...
·
|
|---|
|
Hi @Igor Chekalin (and anyone else interested), this would be the documentation for the fields: https://welcome.astrobin.com/importing-acquisitions-from-csv Do you mind adapting your script to using those fields, and send me some sample data for testing purposes? Thank you! Salvatore |
|
1.20
#...
·
|
|---|
Salvatore Iovene: Hi, Salvatore, thank you for the fantastically quick response! Document looks fine to me. As I understand it, is it ok if not all fields will be present in each row? Only one point is uncertain - the index of filters means a number in the list that the user has set. So we need to define the uniform rule for both user and script in which order to specify filters. One of possible solutions is - to define a standard sequence like "L,R,G,B,H,S,O" and specify it in this order, without swapping, just skipping unused in the session (ex. LRGB, HSO, RGBH, HO etc). Is it already possible to upload data from such a CSV file to the form? I has already updated by script (c++ command line tool actually) and will send you an example of it's output. The tool is currently use my files naming convention set in APT (for each .fits file folder recursively it takes date from file attributes, filter end exp. from file name, then aggregates all by date & filter counting frames. I am going to improve it by parsing FITS headers to make it naming-agnostic, then going to publish it as opensource on GitHub. Here is an example of output file: session.csv Thank you! Igor |
#...
·
·
1
like
|
|---|
Hi Igor,Igor Chekalin: Yes, only the fields that are mandatory in the form are mandatory in the CSV importer too. I will add this information to the document. Igor Chekalin: The filter field refers to a specific filter on AstroBin's equipment database, and it needs to be the ID of the object on AstroBin's database. This ID is part of the URL to the page of that filter. See screenshot:  We cannot simply use "Ha, SII, OIII" etc because the field refers to a _specific_ filter. Igor Chekalin: Not yet but I hope to release it tomorrow! Igor Chekalin: This CSV is missing a header line to tell what each column is  |
#...
·
·
1
like
|
|---|
|
Hi @Igor Chekalin, this is now deployed, feel free to give it a go and please let me know if you spot any bugs! Thanks! Salvatore |
|
1.20
#...
·
·
2
likes
|
|---|
Salvatore Iovene: Works great! Just added 99 lines for 40-nights photo (85 hours of exposition - https://www.astrobin.com/s5uawn/ ) Thank you very much, Salvatore! |
4.21
#...
·
|
|---|
| I was just playing with this. I have a program that walks my subs and creates a csv file. With the current import feature, you have to paste in the csv data itself. This is kinda a pain. How about the option to upload the csv file so no copy/paste is required? |
#...
·
|
|---|
| Given how easy it is to open a file in notepad and copy paste, and the huge list of planned work on AstroBin, I don’t see this happening on the short term, unfortunately. Sorry about that! |
