Closed erikadudki closed 5 years ago
I would also suppose that it makes no sense to have this duplicated functionality in here. @MerktSimon @erikadudki The python code can be deleted, but the simulationSpecification files need to be preserved, right?
visualizationSpecification_Isensee_JCB2018_2.tsv ist still needed even if the routine runs as part of PEtab since it is model specific (i think the other file is just an old version with a mistake). Goal would be to get such visualization files for all the models.
Could you delete the duplicate python files then and only keep the needed visuSpec files? Then this pull request would be ready to merge
This pull request is currently also part of PEtab. So question would be, if this routine should stay part of the benchmark models or access over PEtab is sufficient