-
Notifications
You must be signed in to change notification settings - Fork 7
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
composite problem #265
Comments
Hi @MA-Kochen I'm not too sure about your setup, could you describe your composite problem in a few sentences, and provide the PEtab problem if possible? I could then try to reproduce the error or suggest alternatives. Which tool(s) do you intend to work with for simulation/parameter estimation? |
I have two SBML models (different experiments) with associated data and I'm trying to find a common set of parameters. Each model has multiple sub-experiments which I've defined in the relevant tsv files. I'm using the develop branch of PyPesto with the new roadrunner implementation. Note that I've since redefined the problem as a single PeTab problem (combining the two and using a more extensive experimental conditions file). This seems to have side stepped the issue. Setup looks like this:
The full Traceback is
|
One of the YAML files:
|
Thanks for sharing. I think your current fix is the way to go. Your use case of combining multiple PEtab problems looks uncommon to me, and there is probably little tool support available for it. One approach could be to use the A minor point: you may be able to combine your two conditions files simply by listing them both in the YAML file -- maybe that helps if you are trying to keep the two parts as separate as possible. As long as the condition IDs remain unique across both files, it should be fine. If you try this and want further advice, I would ask for the full set of PEtab files, or a minimal working example (via email is also fine). |
Using the composite problem method returns the following error:
AttributeError: 'CompositeProblem' object has no attribute 'extensions_config'
Suggestions?
The text was updated successfully, but these errors were encountered: