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

Add ability to select Live model or preset data after startup #113

Open
AdrianDAlessandro opened this issue Feb 8, 2024 · 2 comments
Open
Assignees
Labels
backend Related to the business logic of the tool feature Adding new functionality, small or large frontend Related to the user interaction layer (GUI, UI or UX) wontfix This will not be worked on

Comments

@AdrianDAlessandro
Copy link
Collaborator

Problem:
As it stands, the only way to run the vis system with the pre-set data is to run it in develop mode. This presents a couple of issues:

  1. The develop mode requires the entire code to be available so that the docker image can build, instead of pulling the image from github. This means the Live Model version and the Pre-set Data version can be out of sync.
  2. There is no ability to change between live and preset data without going into the machine and manually stopping and starting the container.
  3. Currently, the pre-set data version does not include any WESIM data, so there are no plots from it (like the weather table)

Proposed Solution:
It's possible to add a toggle to the Control view to solve all three of the above. This will require some refactoring, so there probably isn't time for it, but it is possible.

A simpler solution that only fixes 1 would be to create a run_pre_set.sh that runs configure.py with a different argument that runs the production version but does not set LIVE_MODEL to true.

Number 3 can be solved by removing the if LIVE_MODEL statement at the top of data.py

@AdrianDAlessandro AdrianDAlessandro added feature Adding new functionality, small or large frontend Related to the user interaction layer (GUI, UI or UX) backend Related to the business logic of the tool labels Feb 8, 2024
@pclemow
Copy link
Collaborator

pclemow commented Feb 12, 2024

This is a particular problem given the pre-recorded data is likely to be the most common way to run the system. It would definitely be preferable to have it switchable but seperate run scripts for live and pre-recorded would be good too. Is that possible?

@AdrianDAlessandro AdrianDAlessandro self-assigned this Feb 12, 2024
@AdrianDAlessandro
Copy link
Collaborator Author

I can throw the separate run scripts together very quickly, so I will do that. If the toggle turns out easier than I first thought, I'll do that too, but it might end up being a bit buggy.

@AdrianDAlessandro AdrianDAlessandro added the wontfix This will not be worked on label Feb 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Related to the business logic of the tool feature Adding new functionality, small or large frontend Related to the user interaction layer (GUI, UI or UX) wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants