Initial thoughts on 0.1rc1: Much improved integration performance, but have no time to fully test it ;-)
It is painfully and prohibitively slow to load a model or to swap between models. Similarly for cloning a model. This seems true for both simple models with very few variables (i.e. 1952 Hodgkin & Huxley) and more complex models with many variables. If I have a graph V vs time linked to the selected model, I would expect the graph to remain valid when I clone the model and run a simulation. Currently the V variable becomes undefined and I have to reselect the (same) V variable from the list. The time variable remains valid. Once simulations have been run I seem to be able to swap between models and have the graph remain valid. I really dislike the idea of using points/graph to discretise my graphs. I want to be able to say give me a point every 1 ms or every 10 ms. I am not convinced that I need to clone my model just to change the integration parameters and re-integrate. This is especially painful given how slow it is to clone and then select the cloned model. This seems like a feature forced upon the user to support the idea of another client accessing the same model through the cellml_corba_server. Perhaps if it wasn't so slow to change models in the GUI then this wouldn't be an issue. Standard user interface behaviour suggests that when I right click on something but choose nothing from the menu that pops up then either nothing is done or the menu remains visible when I release the mouse button. This is true for most right-clicks I have tried, but right clicking on a model in the model tree will always result in the model rename dialog box unless I specifically choose some option or navigate the mouse away from the menu. If I hold the button down, it is clear that the rename option is not selected, yet as soon as I release the mouse button up pops the dialog box. David. Andrew Miller wrote: > Hi all, > > The first release candidate for CellML API, version 1.0, has been > released. If you would like to ensure that your application works with > the CellML API 1.0 release, please test against the release candidate. > Once a reasonable amount of time has elapsed, and no problems with the > release candidate are identified, the API will be released. Please > report any bugs you find at http://www.cellml.org/tools/api/api_tracker, > or to this list, or directly to [EMAIL PROTECTED] > > Best regards, > Andrew Miller > > _______________________________________________ > cellml-discussion mailing list > [email protected] > http://www.cellml.org/mailman/listinfo/cellml-discussion -- David Nickerson, PhD Research Fellow Division of Bioengineering Faculty of Engineering National University of Singapore Email: [EMAIL PROTECTED] _______________________________________________ cellml-discussion mailing list [email protected] http://www.cellml.org/mailman/listinfo/cellml-discussion
