-
Notifications
You must be signed in to change notification settings - Fork 52
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
Copasi javascript support #2015
Conversation
…JavaScript library. This new feature in SEEK enables interpreting COPASI-supported models directly in the client using this library.
…ted with a model.
…application) when multiple items are associated with a model.
…ser has the right to download the asset.
…e current user, use SpecialAuthCode to enable loading the model into CopasiUI (desktop application)
…lation page. These parameters can now be included when running model simulations, providing enhanced flexibility in configuration.
…ls that are not publicly accessible but available for download by the current user, requiring a special authentication code.
@@ -40,6 +40,6 @@ def jws_online_logo | |||
end | |||
|
|||
def show_copasi_button? | |||
Seek::Config.copasi_enabled && (@display_model.policy.access_type == Policy::ALL_USERS) && @display_model.is_copasi_supported? | |||
Seek::Config.copasi_enabled && @display_model.is_copasi_supported? && @display_model.is_downloadable? && @display_model.can_download?(current_user) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this duplicates and could reuse @display_model.can_run_copasi?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can_run_copasi?
is defined for the "model" model, can not be called by @display_model ( versioning model)
#1939