Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Final elimination of the galilserver/fw-gui forever #48

Open
dsand opened this issue Feb 3, 2022 · 3 comments
Open

Final elimination of the galilserver/fw-gui forever #48

dsand opened this issue Feb 3, 2022 · 3 comments
Assignees

Comments

@dsand
Copy link
Contributor

dsand commented Feb 3, 2022

The issue discovered during the Jan 2022 run is that Azcam pulls header keyword information from the old galilserver/fw-gui. So we need to work with @mplesser to replace this functionality in Azcam to talk to the new galil code.

@dsand
Copy link
Contributor Author

dsand commented Feb 3, 2022

Notes in Feb 3, 2022 agenda from @pndaly

Update on removing galilserver/fw-gui forever: Houston, we have a problem. I have taken a look at this and there are several alternatives each with its pros/cons:
a. Use PyIndi as distributed with INDI. This looks OK but we would have to install all of INDI plus the PyIndi SWIG wrapper (so it needs a C compiler) on the Azcam machine which runs Windows;
b. Use pyindi as written by Scott/Tim at MMT and used by Dan in the web-GUI. This looks like the best approach but looking at the code, it seems very web-oriented which is not what we want. I think I’ll contact Scott about this to see if he can spare some time on a Zoom call to discuss the code;
c. Use GCLIB and produce a Python copy of Galil_DMC_22x0_CLI (which was written in C and works very well). This requires installing GCLIB etc on the Azcam machine under windows. A further drawback is that we would have 2 points of control for 90Prime which we want to avoid;
d. Similar to c) is to write an NG-server and implement the commands identified by Dan/CJ/me. This has promise but has the same drawback as we would have 2 points of control);
e. Move Azcam off the windows machine to a Linux environment?
I think I shall pursue b) further but it won’t be quick so I doubt it’s be available for the Feb run.

@pndaly
Copy link

pndaly commented Mar 3, 2022

Met with CJ, Scott and Dan after the s/w meeting this morning. We ironed out a path forward and Dan/Scott are happy to help. Both points (b) and (d) were discussed and both have merit so we have decided to follow (b) as Plan A and (d) as Plan B. The reason we need a 'Plan B' is we're not sure how and asynchronous class would integrate into Mike Lesser's code. A follow up meeting will be held to check on progress.

@dsand
Copy link
Contributor Author

dsand commented Apr 22, 2022

The new NG-server is working well, both on @pndaly 's end and @mplesser 's with Azcam. As of April 21, we did fix a filter related bug, so I will keep this open for another run or two in case we need to iron out further things.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants