Chronological Thread 

< Chronological >      < Thread >

---

> > When someone opens a CellML model, I want that person to know
> > straightaway whether the model contains errors/warnings, so not an
option.
>
> We are talking about getPositionInXML, not running VACSS validation - you
> can get the list of errors, but it is assigning line and column numbers in
the
> raw XML to those errors that is expensive. Why not just do what the
> xulrunner-based OpenCell did, and show the errors, without a line number,
> and only work out where the error is in the file at the point the user
wants to
> go to the error location?

This wouldn't be perfect, but it would indeed 'address' my issue with
getPositionInXml. Not perfect because, as in OpenCell, you can end up with
many messages that read exactly the same. For example, if I open that
moderately big model in OpenCell, I get many messages that read "Warning:
MathML equals element has inconsistent units between the sides" which from
an end-user's perspective doesn't mean much: no idea where the warning
originated from (unless you in the right view and double click on the
message).

Otherwise, even though getPositionInXml is indeed my current bottleneck,
getValidityError is also somewhat slow...

Alan

---

• [cellml-dev] Very slow getPositionInXML function in VACSS, Alan Garny, 01/19/2012
  • [cellml-dev] Very slow getPositionInXML function in VACSS, Andrew Miller, 01/19/2012
    • [cellml-dev] Very slow getPositionInXML function in VACSS, Alan Garny, 01/19/2012
      • [cellml-dev] Very slow getPositionInXML function in VACSS, Andrew Miller, 01/19/2012
        • [cellml-dev] Very slow getPositionInXML function in VACSS, Alan Garny, 01/19/2012
          • [cellml-dev] Very slow getPositionInXML function in VACSS, Jonathan Cooper, 01/19/2012
            • [cellml-dev] Very slow getPositionInXML function in VACSS, Alan Garny, 01/20/2012

---

Archive powered by MHonArc 2.6.18.