My AstroImaging Planner

Your Observatory & Setup
25

Can’t wait. Thanks Gabe!!

Chris

1 Like
26

I’ve made it publicly available now. You can pull the source here:

The latest image is also on Docker Hub:

I’ve tried to write a detailed Readme, but may have missed something. If you encounter any issues, please let me know!

Gabe

8 Likes
27

The automatic grading of images appears to be doing a decent job. Lots of wind last night, so I expected some frames would be tossed. I found a few that were close to the threshold for tossing out, and sure enough, the stars looked slightly elongated vs. the others in the batch for the same target. Will continue to test it out in the coming weeks.

Gabe

3 Likes
28

Hi Gabe,

I have downloaded your docker image and I cannot make it work. I think the issue is the fits directory structure you expect: {target_name}/{date}/{fits_files} and I am storing the files like this {target_name}/{filter}/{fits_files}

Is it mandatory to store the date as part of the dir’s path?

Cheers,

José

1 Like
29

Thanks for letting me know! Can you show a copy of the error? That’ll help me track it down.

30

One point of clarification is that while you can use the docker image from docker hub, to get it to work, you will need to have a copy of the files in the conf directory that’s on the github repository. You can edit those files as needed, but it should give you a good starting point. If you don’t want to use the command line to start the container, you can use the docker interface. Once you start the image, you can add more options. Here’s an example configuration that I used with that approach:

Screen Shot 2020-10-28 at 4.11.12 PM
Screen Shot 2020-10-28 at 4.11.12 PM599×573 28.4 KB

Where each Host Path entry is on my computer, and the Container Paths entries shouldn’t change. They’re listed as:

  • Path to the conf directory that contains the config.yml, equipment.yml, and target_status.yml (which is initially empty, but gets populated on the first run)
  • Path to the data directory
  • Path to your roboclip file, which is typically C:\Users\UserName\Documents\Voyager\Data
31

Hi Gabe,

As soon as I get home tonight I share with you the error log and my conf files. I have a similar setup like yours, a remote windows computer that syncs the data back to a Mac. I am running docker inside my Mac and pointing to the local copy of the fits and Voyager conf files.

Thanks,

José

32

Hi Gabe,

I have checkout your git repo and modified the conf files accordingly and I get this error:

Joses-MacBook-Pro:TheAstroImagingPlanner jmtanous$ docker-compose up
Creating network “theastroimagingplanner_default” with the default driver
Creating theastroimagingplanner_app_1 … done
Attaching to theastroimagingplanner_app_1
app_1 | 2020-10-31 00:26:12,361 font_manager Generating new fontManager, this may take some time…
app_1 | 2020-10-31 00:26:13,007 app Updating Data
app_1 | 2020-10-31 00:26:13,156 data_parser Reading stored fits files
100%|██████████| 521/521 [00:02<00:00, 186.99it/s]
app_1 | 2020-10-31 00:26:15,991 data_parser Read 521 files
app_1 | Traceback (most recent call last):
app_1 | File “./app.py”, line 164, in
app_1 | update_data()
app_1 | File “./app.py”, line 145, in update_data
app_1 | df_stored_data = get_data_info(data_dir=DATA_DIR)
app_1 | File “/app/astro_planner/data_parser.py”, line 125, in get_data_info
app_1 | df_files = clean_file_list(df_files)
app_1 | File “/app/astro_planner/data_parser.py”, line 222, in clean_file_list
app_1 | df0 = df[
app_1 | File “/usr/local/lib/python3.8/site-packages/pandas/core/frame.py”, line 2908, in getitem
app_1 | indexer = self.loc._get_listlike_indexer(key, axis=1, raise_missing=True)[1]
app_1 | File “/usr/local/lib/python3.8/site-packages/pandas/core/indexing.py”, line 1254, in _get_listlike_indexer
app_1 | self._validate_read_indexer(keyarr, indexer, axis, raise_missing=raise_missing)
app_1 | File “/usr/local/lib/python3.8/site-packages/pandas/core/indexing.py”, line 1304, in _validate_read_indexer
app_1 | raise KeyError(f"{not_found} not in index")
app_1 | KeyError: “[‘EXPOSURE’] not in index”
theastroimagingplanner_app_1 exited with code 1
Joses-MacBook-Pro:TheAstroImagingPlanner jmtanous$

Thanks,

José

33

Ah, interesting. I was basing my filters off files written by Voyager. Do your fits files have another field that replaces EXPOSURE to indicate subexposure length? Would you mind sending me one of your fits files that’s throwing the error?

Gabe

34

Absolutely,

This zip file contains a fits that triggers the problem. The zip file also keeps the same dir structure I am using to save the files.

Cheers,

José

1 Like
35

Thanks so much! I found the issue. I’ll issue a new version soon. I found a fix, but want to make sure I’m catching other similar issues with FITS header entries being different than what I’d expect. Here’s an entry on the table of your NGC 104 sub.

Screen Shot 2020-10-30 at 11.30.38 PM
Screen Shot 2020-10-30 at 11.30.38 PM1320×154 13.2 KB

Cheers,
Gabe

2 Likes
36

Let me know if you need extra testing. I have 3 Voyager system and they use different capture interfaces, I’ll be happy to do some testing.

Cheers,

José

1 Like
37

Should have a new version up w/in the hour :slight_smile:

38

A new version is on docker hub. You can pull it with

docker pull gshau/astroimaging-planner

Also, please check the new config.yml file with additional mappings for the FITS Header fields. The issue with the FITs files you had was using EXPTIME instead of EXPOSURE. In the mapping below, you can specify the FITs field for your files. If multiple items are listed under an entry (e.g. two are under exposure), they’re all used since you can have multiple files w/ different formats.

Hope this helps, and please let me know if you encounter any other issues.

Cheers,
Gabe

39

Thanks Gabe,

It works!

I still have some issues regarding the graphs. I will play with your planner tomorrow and try to figure out why the graphs are not working.

Cheers,

José

1 Like
40

Just to let others know, we found the issue for getting plots working for Jose. It was a simple fix with the configuration file. If anyone else has any issues getting up and running, please let me know.

2 Likes
41

So far so good, this project is very useful, specially for balancing big mosaic projects!

Thanks for sharing the project and for your help on setting it up.

Cheers,

José

1 Like
42

Hello AstroGabe,

This is a fantastic contribution.
And i’ve no words to express my gratitude !

I will definitly give a try and time investment in your planner software as soon as possible, when other auxiliary things will be fixed in our remote observatory.

–
HoxCa

1 Like
43

I’m making progress towards a more granular review of stored files, including all FITs header data and measured star data including FWHM, Eccentricity and distributions of these across the chip. This is a step towards the automatic image grading that I want to implement.

I was having difficulty with wind one night on M31 below, and you can tell in the scatter plot for the luminance files where I had large eccentricity and FWHM.

Screen Shot 2020-11-21 at 5.06.38 PM
Screen Shot 2020-11-21 at 5.06.38 PM1411×1324 146 KB

4 Likes
44

I’ve finally got around to making a demo video. I’ve also added a new section that inspects all the frames that you have to give more insights about your imaging rigs. The expectation is that eventually, automatic grading will be reflected in the exposure progress on the first tab. I also have a standalone web app if you just want to inspect on an ad-hoc basis.

Here’s the video:

7 Likes