>>>> I'm really not sure how to address this other than suggesting that >>>> applications clearly state their units support status and provide >>>> some way to easily locate (and view?) instances where unit >> conversion >>>> factors have been added to the model (either at the >> connection level >>>> or within equations). >>> To make it simpler in terms of user interface, I think it should be >>> done at the connection level. At least, that's where we >> intend to do it in COR. >> >> except that most of the generated units conversion factors >> could easily be buried inside equations where they are hard >> to spot with the naked eye...for example, this sort of >> equation can give you widely different results without the >> need for any units corrections at the connection level: >> >> a [mM] = b [uM] + c [mM] >> >> but would presumably result in (b*0.001) within the equation... > > Ok, maybe I misunderstood what you meant by units correction at the > connection level then. I, personally, intend to do 'b*0.001' when computing > the model, but not show/tell it to the user when s/he edits the model, so > that s/he doesn't get confused.
yep - thats the sort of behaviour I would expect, but its also the sort of behaviour that will be very application specific and provide unwary users of CellML models with inexplicably different results for the same model in different applications. Which I'm guessing is why you suggest this sort of behaviour needs to be enforced in all CellML compliant applications... -- 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
