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

Allow to use first run simulations for subsequent runs of a given element space #20

Open
3 tasks
pedrobcst opened this issue Mar 28, 2022 · 1 comment
Open
3 tasks
Labels
core Related to xerus core

Comments

@pedrobcst
Copy link
Owner

Currently, everytime the analyze function is ran (even if the same paremeters), Xerus will re-simulate, re-query the database. This can be time consuming, and actually makes the sometimes needed iterative process of hyperparameter tuning (ie, g, delta, n_runs, provider settings and so on) time consuming. In light of this problem, the following changes are needed:

  • After the first run, keep track of the already simulated patterns / correlations. (should be almost there..)
  • If this simulations already exist, use them instead of re simulating / re - querying
  • Keep a 'safe' information of simulations / structures that can always be accessed to be used for filtering purposes
@pedrobcst
Copy link
Owner Author

Also, It would be benetifial if we could pre-simulate the simulations for viz purposes only, so the pre simulated + correlation calculation can be used (for example in the Streamlit interface) before running the full analysis. Sometimes this is enough to get a good idea what is in the sample. This pre run of simulation+correlation, should be carried over then if analyze is run, it will use this pre-simulated data.

@pedrobcst pedrobcst moved this from To do to In progress in Xerus main development Apr 15, 2022
@pedrobcst pedrobcst added the core Related to xerus core label Apr 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Related to xerus core
Projects
Development

No branches or pull requests

1 participant