custom function in Assembler results : how to pass the current window as argument

Laurent,

This doesn't make sense. Output expressions are normally evaluated in a background process (when using either LSCS or ICRP) except in the case where a single simulation is performed and "optimise single job run" is used. Because of that, there's no window or access to the maestro/ADE XL session in the function.

What exactly are you trying to do that requires the window or session?

Andrew

Hello Andrew,
Thanks for you answer.
My custom function will run a python script. This script needs as arguments some outputs of the simulation.

So I need to know to know the rdb in order to (at least) get the simulation's outputs directory.

Does that make sense to use the output expression like that?

Laurent

and I don't know how to get the rdb without starting from the current window (or fnxSession)

Why do you need to get the rdb? The rdb won't have been written at the time of point evaluation (and anyway, it's written in the parent Virtuoso not at the time the result is evaluated).

Regards,

Andrew

Why do you need to get the rdb? The rdb won't have been written at the time of point evaluation (and anyway, it's written in the parent Virtuoso not at the time the result is evaluated).

Regards,

Andrew

kkdesbois said:

My custom function will run a python script. This script needs as arguments some outputs of the simulation.

Sorry - didn't see the earlier post (there's a bug in the forum software we use which still hasn't been fixed despite us reporting it to the vendor over several years) where they don't use unique message ids in the email notifications which means that some email clients don't see all the emails (if they index on the message id, which is supposed to be unique). 

My point about the rdb is still valid, but you could use asiGetPsfDir(asiGetCurrentSession()) or asiGetNetlistDir(asiGetCurrentSession()) to retrieve where the simulation results are located for that point.

Andrew

Andrew,

I think that it's a good point to retrieve the needed informations thanks to the asi functions. I'm going to try that.

Unfortunately, I will get the information only for the current test where the output expression is written.
And I need also to pass to the python script the name of a file stored in the psf directory of another test (of my assembler session).

Ex: Assembler session is test1 and test2. test2 starts when test1 is over (thanks to calcVal)
In the output expressions of test2, I use my custom function which runs the python script. But this script needs as arguments the name of files stored in the psf directory of test1 and test2.

Anyway, from the current psf directory, I can go back to the other test's psf directory. I don't like that much because in case of Cadence decides someday to change the location of the tests' results directory.

Thank you for your good advices. I'll keep you aware.

Laurent,

You could have an output of test1 (say called "psfdir") which is asiGetPsfDir(asiGetCurrentSession()) and then use calcVal in the test2 expression to retrieve that - so your test2 function could be myFunction(asiGetPsfDir(asiGetCurrentSession()) calcVal("psfdir" "test1"))

Andrew

Andrew,

It works very well and as I expected. Thanks again for the support and the tips.

By the way, is there a skill function to hide the created "psfdir" outputs in order not to pollute the user's results window.

Ideally, the best would be to make also invisible the output definition in the tab "outputs setup"

kkdesbois said:

By the way, is there a skill function to hide the created "psfdir" outputs in order not to pollute the user's results window.

Unfortunately not.

Andrew

What a pity :(

Thanks.