Question-and-Answer Resource for the Building Energy Modeling Community
 | 1 | initial version |
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: -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); -it reads the location name in the first line of the epw file; -depending on the location name it appends a different group of objects to the in.idf file.
| | 2 | No.2 Revision |
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:
-it 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);
-it 2) it reads the location name in the first line of the epw file;
-depending 3) depending on the location name it appends a different group of objects to the in.idf file.
| | 3 | No.3 Revision |
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.
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.
