<@U03SDTNCQEB> if Xyce is started on netlist circu...
# xyce
s
@Joshua Smith if Xyce is started on netlist circuit.spice with a raw filename using
-r circuit.raw
(
Xyce circuit.spice -r circuit.raw
) , simulation data goes there and this is fine. However a .PRINT line in the netlist with format=RAW and no FILE specification will use
circuit.spice.raw
, creating another raw file. Is this intended? a -r command line should reset the default output filename in my humble opinion. Of course this is not a severe issue as i can work around this by setting FILE=circuit.raw explicitly.
e
For all the formats that can be specified on the
.PRINT
line, the convention in Xyce has always been to append a suffix to the full netlist name, including the original suffix. So, if the original file is netlist.cir, and STD format is specified, the resulting file is is netlist.cir.prn. Same with (for example) format=probe, or format=csw. They will produce netlist.cir.csd and netlist.cir.csv, respectively. So, when we added support for rawfiles, we continued with this pattern.
Regarding raw files; from what I remember, if you specify a rawfile name on the command line via -r, and also specify format=raw on the .PRINT line, I thought it would use the name specified on the command line, but put the specified variables from the .PRINT line in that file. But maybe I am mis-remembering that detail.
s
I will do some checks, whatever the behavior i can specify the file location when needed so no problem. Thanks
👍 1
e
Anyway, it has been a very long time since we adopted the
full.name + suffix
approach that I don’t recall who came up with the idea (it could have been me, or possibly not), or if it was decision we put much thought into at the time. In the early days (20+ years ago) we weren’t as concerned with compatibility.
If other codes don’t do this for default behavior, it is probably something we should think about. But it would probably mean modifying 90% of our test suite. 🙂
s
No, don't do that, the best is to have the possibility to specify output file names. Different tools have different conventions so there is no one-fits-all anyway.
👍 2