-
Notifications
You must be signed in to change notification settings - Fork 25
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 implementation on new XLMOD STRUCTURE: #77
Comments
Can you please provide additional information? Currently it's unclear what is leading to the error. Please include details on how you got this error and include a full stack trace. |
hi @bittremieux ,these are some additional details regarding the error ,there are various areas in the code where we are using the cache directory is leading to errors because they are not able to import CV's from it like there was a assertion error here and similarly othere issues are occuring due to cache directory ,as we have disabled it here due to some reasons ,so i feel adding a temorary cache directory support would be nice for all the modules while testing so we can ensure that these funtions are working fine . there are some of the trace for it . |
These three errors all refer to terms from the XLMOD controlled vocabulary. Did you get errors for terms from any of the other CVs (e.g. UNIMOD or PSI-MOD)? This seems rather related to XLMOD specifically rather than the caching. Additionally, please try to manually clear the cache directory to make sure that the issue is not due to a corrupted download. |
hi @bittremieux ,u were right first three errors are due to the XLMOD ,due to its updation .I was not able to find XLMOD:02001 in the provided link as it is being updated .second the assertion errors (fourth one ) we were facing because the XLMOD structure is being changed ,so our parsng logic is returning zero for XLMOD which eventually cause the error > |
it would be great if we can add a temporary cache directory support for all modules while testing .
The text was updated successfully, but these errors were encountered: