-
Notifications
You must be signed in to change notification settings - Fork 10
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
Update the README to specify which Qurro version should be installed based on your QIIME 2 version #328
Comments
Hello, Successfully uninstalled altair-5.0.0 Does anybody know whether downgrading altair will interfere with other qiime2 plugins? Best, |
Based on searching through the QIIME 2 codebase, I think the only command in the core distribution of QIIME 2 that uses Altair (at the moment) is It looks like downgrading Altair causes some problems for
So, for the time being:
Eesh -- sorry for the trouble! This problem should be resolvable by updating Qurro to work with newer versions of Altair -- this is discussed in #216. I'm swamped with other projects right now, so I can't promise a quick resolution to this problem :(, but hopefully the information above is sufficient in the meantime. |
Hi, |
Hi @fedarko |
Thank you for letting me know—I wasn't aware of that change. Since it seems like this incompatibility exists at the level of QIIME 2, it seems like the workarounds will have to occur outside of Qurro. If you have a QIIME 2 artifact (let's call it X) from QIIME 2 2023.5 or newer that you'd like to use with Qurro in an older version of QIIME 2, I guess the easiest workarounds are:
Neither of these workarounds are ideal, I know -- the first will remove provenance information from X, and the second will remove provenance information from X and from your other QIIME 2 artifacts. The ideal solution to this is problem will be updating Qurro to work with the later version of Altair that QIIME 2 2023.5 uses (#216), which will then allow Qurro to be installed into QIIME 2 2023.5 (and thus negate this problem). The existence of this problem makes this update more urgent—I'll try to set aside some time soon to fix this. Thanks again for the note. |
Hi @fedarko I have used gemelli (instead of deicode to circumvent the np.int issue) in conda env q2-amplicon-2023.9. |
Thanks @ARW-UBT! I apologize -- it's been a busy period here (wrapping up other research projects, finishing my thesis, other duties...), so I have not yet gotten around to resolving this issue. I'll try to move it higher up in my priorities, since this is causing problems with other tools' workflows. For what it's worth, I tried to install the latest version of QIIME 2 on my laptop today in order to start testing this -- and of course ran into all sorts of problems with my now-out-of-date version of conda :) So I'm going to have to take a bit to remember how this infrastructure works... |
Hi @fedarko |
Any update on this @fedarko? |
Sorry -- not yet. I've been swamped with other tasks for now. I will try to get this addressed as soon as I can. |
See the discussion here.
Option 1: adjust the "system requirements" section (maybe put this beforehand, and just have the system requirements section talk about python version & browsers?)
Option 2: just add an extra parenthetical to the "system requirements" section --
The second option is more elegant, I think, but the first option is more obvious.
The text was updated successfully, but these errors were encountered: