-
Notifications
You must be signed in to change notification settings - Fork 27
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
SBML connection problem #740
Comments
There is a more general issue of sbml processes not being allowed to take in multiple inputs or multiple outputs (except association / dissociation, those are allowed to give out only 1 output but can take unlimited inputs). This is probably relevant to this issue. |
Associations take 2 or more inputs and output 1. Dissociations do the reverse and take only 1 input, producing at least. Constructing a compound molecule (i.e. a complex) vs. decomposing it back. From what I can tell dissociation works fine. Associations can also take multiple inputs but no output can be constructed. All other process node types seem to have problems taking multiple inputs or outputs, except truncated processes which can produce multiple outputs. So, things are pretty random / messed up for some reason. |
@ugurdogrusoz This behavior you described above was also implemented into the export functionality. I changed those so that we can have the wanted behavior as part of #712. |
@ugurdogrusoz No, I am not saying that. I am saying that the export functionality was made with this in mind. It is now changed though. When this issue is fixed, we won't have to change the export (most likely). That's what I am saying. |
Original problem with protein, process and AND node connections are fixed but:
|
In case we have a protein, process and AND node, if we first connect AND to process via a catalysis edge, then we cannot connect protein to process via a consumption edge. However, if we first connect protein to process via a consumption edge, then we can connect AND to process via a catalysis edge. We should be able to connect consumption edge in the first case as well.
The text was updated successfully, but these errors were encountered: