Jaime Souza

I had the same problem.

Hi The xml files for model serialization is a great idea. It is a very wise solution. The html will only help the debug (locally). Tks, Jaime

The version control can be added. I believe what you meant is that .xsl and .css file names include the version, i.e.: dae-tools-1.0.xsl and dae-tools-1.0.css and the .xml reports link the appropriate version. Am I right? Yes. The reason: at the time I developed model reports the loading .xsl from a different domain was not allowed in the browser (same-origin security policy). Yor are correct. It is still not allowed to have xml and xsl in different domains. Maybe you could create a SaveModelReportHtml()...

Hi Dragan, The idea is that a single call to the SaveModelReport() could generate multiple XML (one for the main model and the others for its components). If so, you should consider that the name of the component xml file includes the hierarchy or the tree (like a breadcrumb). I think it would be great to have it in your new release. I have another suggestion: to include version control to the XSL and CSS files, to publish your XSL and CSS files in the daetools.com and to point these URL in the XML....

Hi Dragan, I have tried moving the position of the elements as you said, but It didn't solve. So I changed the XSL, as shown in the attached where I commented my changes. As I said before my model has an "empty" base model that other Components (using the same nomenclature of the XSL. The variables, parameters and all the stuff are inside these Components. So the XSL I propose is recursive in the Components nodes. Here is the example case with this new XSL (I have to publish this because the my browser...

Problems with XSLT transformations in complex models

Hi Dragan, You are correct. It works if I run python -m daetools.dae_plotter.plotter previously. Thanks Jaime

'Cannot connect TCP/IP data reporter' when using MacOS