-
Notifications
You must be signed in to change notification settings - Fork 6
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
Run on Windows? #27
Comments
It looks like the |
Ok, that feedback identified the problem and solved a mystery. When I attempted to run the app initially (and got these errors), I noted that there was NO input_properties.cfg file present in the folder where I was running the app from. I copied over my working .cfg file from the linux computer but the errors were exactly the same. Following your reply above, I searched the ENTIRE computer for any instances of input_properties.cfg and found the old MinXSS-1 version in:
... when I renamed that file to in effect remove it from the computer and re-ran the current app, a properly-formatted input_properties.cfg file was created in:
... and the application GUI launched successfully. Would it be possible (and probably recommended) for the .cfg file to be created in whatever folder the user is running the application from & not hard-coded to a specific location? |
Additional: Please note that the folder path used on the Windows platform for OUTPUT and LOG files also appears to be hard-coded to the
location. |
Yes it is sort of hard coded in there to always be in that specific location. That came about because the built application will actually fail to even launch if it's set to the current directory (this is what it was originally). I think it has to do with permissions in the directory that the application runs or something. There's got to be a way to have it both ways... I keep trying to think of a way to add/use a user specified working directory path to the Input/Options but keep running into issues that have already caused crashes in the past. I'll keep thinking about this one. |
On Windows 7 (64-bit), after installing the latest Python-3 (Python 3.7) and all the modules that were reported missing when attempting to run:
python minxss_beacon_decoder.py
Here is the output (followed by commands showing the currently running commit version and python version installed):
======
C:\Users\CSI\Apps\MinXSS_Beacon_Decoder>git show --oneline -s
9998410 (HEAD -> master, origin/master, origin/HEAD) Auto updates output files when user changes ground station parameters
======
C:\Users\CSI\Apps\MinXSS_Beacon_Decoder>python --version
Python 3.7.0
======
Kindly advise if there are additional items required to run the current code on a Windows system.
Thank you!
The text was updated successfully, but these errors were encountered: