Revision history [back]
Just in case someone will need it, I solved the problem in this way: I wrote a python script (as suggested by Yi Zhang), included in the parameter tree. The script performs the following simple operations: 1) it opens the in.epw file in the job folder (I thought that was easier than extracting the job name, but that's up to you); 2) it reads the location name in the first line of the epw file; 3) depending on the location name it appends a different group of objects to the in.idf file.
Just in case someone will need it, I solved the problem in this way:
I wrote a python script (as suggested by Yi Zhang), included in the parameter tree.
rvx file, with "onEachJob" : true.
The script performs the following simple operations:
1) it opens the in.epw file in the job folder (I thought that was easier than extracting the job name, but that's up to you);
2) it reads the location name in the first line of the epw file;
3) depending on the location name it appends a different group of objects to the in.idf file.
Just in case someone will need it, I solved the problem in this way:
I wrote a python script (as suggested by Yi Zhang), included in the rvx file, with "onEachJob" : true.
The script performs the following simple operations:
1) it -it opens the in.epw file in the job folder (I thought that was easier than extracting the job name, but that's up to you);
2) it -it reads the location name in the first line of the epw file;
3) depending -depending on the location name it appends a different group of objects to the in.idf file.