-
Notifications
You must be signed in to change notification settings - Fork 6
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
[BUG] ISA sheets not displayed AND needs extremely CPU usage? #216
Comments
BTW |
Can you tell us an ARC on which we can test it? |
yes, try Frederik Sommer |
Hei, then open in the arcitect and fill the ontologies to have a green check. that was my workaround for not being able to reuse already written isa files that worked fine in v35 maybe this is now a problem? (using excel and old swate) but cannot do anything now since it always throws the error above |
Swate in excel is really old, there were a lot of changes. We tried to be as backwards compatible as possible, but it is not recommended to use the swate in excel at the moment. @Etschbeijer is currently working on restoring Swate in Excel (progress can be tracked here: https://github.com/nfdi4plants/Swate/milestone/9). Swate will receive an update tonight/tomorrow. This might fix some of the issues you encountered |
@frsommer i would need an invite (https://git.nfdi4plants.org/frey1) |
Okay, i checked the ARC:
This was an issue with the database, resolved by @Zerskk ❤️
This issue is due to some underlying changes in our core code (ARCtrl). Swate was not yet ready for the change but had to implement it for other features. This issue will be resolved in the next Swate update (tonight, or tomorrow). Swate cannot display
This issue might be related to #215 on MAC and is currently investigated. Sadly, it is difficult to narrow down, as we are currently not able to reproduce the performance issue: |
Hey @frsommer, does this problem still persist with the current version of ARCitect (0.0.41)? |
I guess the newest ARCtrl and SWATE versions solved this issue. Please feel free to reopen the issue. |
OS and framework information (please complete the following information):
Describe the bug
] Screenshots
The text was updated successfully, but these errors were encountered: