S
Svenn Are Bjerkem
Guest
Hi,
I have been looking into saving some operation points to a file:
dfasdfasdf info what=oppoint where=file file="../psf/%C:r.info"
will create a file named input.info in the ../psf directory when the
whole thing is run through ADE. When the corner tool runs, this is
nice because after a corner is run, then the ../psf directory is moved
or copied to ../Corner/"corner"/psf, hence the input.info file for
this particular run is automatically backed up, and I can inspect
operating points in the input.info files in the Corners hierarchy.
The same does not work for monte-carlo, as monte-carlo renames family
members to mc1-001_dc.dc, mc1-002_dc.dc etc. My file is still called
input.info only, as there seem to be a bit more complicated backup
code in function here.
I need a way to back-up the input.info file before the next montecarlo
run starts. I haven't found that way yet, maybe somebody here has had
the same problem?
--
Svenn
I have been looking into saving some operation points to a file:
dfasdfasdf info what=oppoint where=file file="../psf/%C:r.info"
will create a file named input.info in the ../psf directory when the
whole thing is run through ADE. When the corner tool runs, this is
nice because after a corner is run, then the ../psf directory is moved
or copied to ../Corner/"corner"/psf, hence the input.info file for
this particular run is automatically backed up, and I can inspect
operating points in the input.info files in the Corners hierarchy.
The same does not work for monte-carlo, as monte-carlo renames family
members to mc1-001_dc.dc, mc1-002_dc.dc etc. My file is still called
input.info only, as there seem to be a bit more complicated backup
code in function here.
I need a way to back-up the input.info file before the next montecarlo
run starts. I haven't found that way yet, maybe somebody here has had
the same problem?
--
Svenn