-
Notifications
You must be signed in to change notification settings - Fork 145
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
Default state for anvi-interactive #211
Comments
This is awesome, Ozcan. However, there is one thing I would like us to do something about. Here is what I do:
this results in this error: the reason to that is because the initial run where the state was saved was run with this command:
where One way to deal with this could be a more flexible way of matching state info to available layers. Alternatively, we can check whether state is compatible with available layers, and show a small info on the top right saying "the state is not compatible with the current layers", and fall back to the default plan (as of What do you think? |
Hey Meren, I followed the steps but could not reproduce the problem, here is a screencast: https://www.youtube.com/watch?v=WOojJKIK_aY |
This is very weird..... I did the exact same thing, and had the same problem again. What software did you use for that screencast? So I can do the same and show it to you :) |
I have used built in quicktime for screencast. Can you send me test-output directory maybe i can reproduce the error that way? |
Thanks for looking into this Ozcan :/ The test directory is attached. When I simply run it like this:
And load the
PS: Clearly the newly added parameter |
"attached". Lies... Here: |
Awesome, Ozcan! 217146b resolves this completely. And you are correct, those ad-hoc stuff only modify default values, and not the state. If you don't want to fix that I can correct this. Thank you! |
There must be an option to load a default state while calling
anvi-interactive
.If it is not there, it shouldn't load anything, if it is there, it should load the state and call draw immediately (since there is a state, the user will unlikely change anything before clicking 'draw', so let's do it as well).
Best,
The text was updated successfully, but these errors were encountered: