Re-loading (and/or controlling) History Items in ADEXL view

...And compounding what Andrew replied in my other query about saving results, I found a nice

axlViewResDB()

which allows to navigate through the results stored in the simulation folder...That is already quite a help!

To couple it with my other query about saving ADE XL outputs to file, I suppose once I open these DB's, I'd be able to save results from them?

Cheers,

Michele

Michele,

This isn't really possible without Ninja-grade hacking, I'm afraid. Even then I'm not convinced it would be worth the effort (it would entail quite a lot of manual work)... it also would be incomplete too because not all the information is necessarily stored in the simulation results directory.

Regards,

Andrew.

Hi Andrew,

not sure what you are qualifying as Ethan Hunt level:

re-inserting history items in the ADE XL view, or

saving to file from a resultsDB?

I wrote the answer below thinking more of the second item...

Hi Andrew,

ok I'm sure that what you are figuring out is pretty Ninja, but I was more thinking of the layman approach...

In this very blurred view of mine, opening results database just pops up the information I'd like to save. It is a matter of dragging a big

rectangle over the data and copy-pasting them. From that to saving these through a few calls to clever functions, did not seem too daunting.

But maybe it is, in practice.

The way I was thinking of doing it, which I think is cumbersome by the way, is by:

1 - opening the ADE XL view that does not have the results in the history, but does have the output definitions

2 - save the outputs to file (for a given test of interest)

3 - automatically (!) convert the outputs format to an ocn type of my_var = my_function type of definitions, then add an fprint()

statement with the variables to be output, mimicking the CSV format.

4 - prepend the file generated in 3 with a OpenResults()

load

This should work although as I say, it is much more work in set up than just finding the way to reinsert the DB handle into the ADE XL view and go from there...

Thanks for bearing with me ;-)

Michele

Michele,

Michele Ancis said:

just finding the way to reinsert the DB handle into the ADE XL view and go from there...

This is the bit which requires the large-scale hacking. There's no "just" about it. It's more than just a handle - the history contains all the state information, pointers to results locations, and various other things - and there aren't public APIs to do all this anyway. It could be done, but it's really a good way of corrupting  your ADE XL database if you get it wrong.

The RDB viewer that you used doesn't have an export, but what you could use is similar to code that I pointed you at before:

In that post, go down to the bit starting axlReadHistoryResDB, and from that point onwards you can see the code to traverse the result database and then print it out. Rather than using axlReadHistoryResDB, you could use rdb=axlReadResDB("/path/to/Interactive.2.rdb") - you don't have to have an ADE XL view open to do this. If all the data you want is scalar, this should be pretty straightforward. 

This approach shouldn't be Mission Impossible ;-)

Regards,

Andrew.