Replies: 14 comments
-
|
Nutmeg script doesn't support paths relative to schematic directory. The paths are resolved relative to simulator execution directory. Usually $HOME/.qucs/spice4qucs. It is changed since #658 Use the absolute paths instead. |
Beta Was this translation helpful? Give feedback.
-
|
This is really a show stopper and brings a lot of trouble into project organization. |
Beta Was this translation helpful? Give feedback.
-
|
Can we allow relative path in nutmeg block on schematic and convert path to absolute while creating ngspice netlist? |
Beta Was this translation helpful? Give feedback.
-
|
Maybe it is a solution: ngspice works with both: the relative path as shown above and the absolute path (in may case): ~/Projects/spice/Verilog-A/VA-Models/osdilibs/ekv3.osdi. Can't understand why qucs-s didn't work - the generated netlist.cir with relative path simulates with ngspice on cmdline in the schematics folder ~/Projects/spice/Verilog-A/VA-Models/examples/ekv/qucs-s_prj/ very well. |
Beta Was this translation helpful? Give feedback.
-
|
To me, for "portability" one should put every file/model needed for a project into the same project folder. Countless problems trying to recreate others work due to missing files or long file paths only relevant on the authors PC has only reinforced this belief. This issue is common to Qucs, Qucs-S, QucsStudio, LTspice and every CAD program I have ever used. Let's not get into Windows versus Linux issues... Is there a special version of ngspice needed for this project? I'm getting "Unknown model type ekv3_rf " errors.
|
Beta Was this translation helpful? Give feedback.
-
|
@tomhajjar : |
Beta Was this translation helpful? Give feedback.
-
|
I'm confused. This schematic and most of the others in this project don't contain the Nutmeg script to load ekv3.osdi. Do only the schematics with the Nutmeg script work? I assumed this project was like EKV3_xyce_prj... |
Beta Was this translation helpful? Give feedback.
-
|
Yes - this is the problem: Thread name is "Relative path in Nutmeg script". It is not functional - qucs-s disturb the input path of ngspice for the osdi lib. You can give the absolute path in Nutmeg script, make a copy of the osdi file as said or wait for other solutions. |
Beta Was this translation helpful? Give feedback.
-
|
Generously Holger has implemented in ngspice developer branch the request to the environment variable NGSPICE_OSDI_DIR which allows pre_osdi commands without path in qucs-s schematics Nutmeg script. This will released in next ngspice release 43. |
Beta Was this translation helpful? Give feedback.
-
|
Wondering why XYCE natively supports EKV3, MOS Level 301 but ngspice doesn't natively support EKV2.4, MOS Level 44 or EKV3, MOS Level 301? |
Beta Was this translation helpful? Give feedback.
-
|
I can guess about EKV - it was closed source until recent times |
Beta Was this translation helpful? Give feedback.
-
This could be done in a two ways, but both has many disadvantages.
The Nutmeg script is a feature for advanced user and should be avoided in a normal schematics. So, I am inclined to keep the things as is because of mentioned above disadvantages. The best solution will be to implement an OSDI library block that will work similar to existing .LIB block. The file devices can resolve the relative paths after #640 |
Beta Was this translation helpful? Give feedback.
-
|
I am moving this issue to Discussion/General |
Beta Was this translation helpful? Give feedback.
-
|
Yes - another library block based on file device could be a solution. |
Beta Was this translation helpful? Give feedback.
-
How can I use relative path for osdi shared libs?
The generated netlist file works with ngspice on cmdline very well. But qucs-s complain about missing file:
Ngspice started...
Error opening osdi lib "../../../osdilibs/ekv3.osdi": No such file or directory!
Error: Library ../../../osdilibs/ekv3.osdi couldn't be loaded!
Beta Was this translation helpful? Give feedback.
All reactions