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

Framework to compare WTs #105

Closed
FatimaPillosu opened this issue Sep 30, 2020 · 1 comment
Closed

Framework to compare WTs #105

FatimaPillosu opened this issue Sep 30, 2020 · 1 comment
Assignees
Labels
enhancement New feature or request priority 2 Issue is in the core functionality or is affecting 60% or more of people using the app.
Milestone

Comments

@FatimaPillosu
Copy link
Contributor

It would be very useful to have a framework in the software where it would be possible to display the WTs from two different DTs. This would be a very useful feature to have, for example, in case of evaluating whether or not change DT when there is a new forecast cycle. It will also be very useful to be able to highlight those WTs where the user thinks there is some significant difference in the WTs, and being able to display that in the DT. This will be a very useful diagnostic tool.

Define the UX of the framework to use for comparisons. Provide a way to load existing DT into an interactive comparison tool.

@FatimaPillosu FatimaPillosu added the enhancement New feature or request label Sep 30, 2020
@FatimaPillosu FatimaPillosu added this to the Enhancements milestone Sep 30, 2020
@onyb onyb added the priority 2 Issue is in the core functionality or is affecting 60% or more of people using the app. label Dec 2, 2020
@onyb
Copy link
Contributor

onyb commented Jan 4, 2021

Added in v0.19.0. It basically allows the user to spin up as many GUI windows as he/she wants, like this:

$ ./ecPoint-Calibrate-0.19.0.AppImage         # first window
$ ./ecPoint-Calibrate-0.19.0.AppImage --fork  # subsequent windows

I'll close this for now, but if the fix is not enough, please feel free to reopen it.

@onyb onyb closed this as completed Jan 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority 2 Issue is in the core functionality or is affecting 60% or more of people using the app.
Projects
None yet
Development

No branches or pull requests

2 participants