OpenStudio workflow not producing in.json however Eplus does

asked 2024-12-20 10:43:10 -0600

antonszilasi
1583 ●1 ●6 ●13

updated 2024-12-21 14:58:37 -0600

14275 ●87 ●25 http://bigladdersoftware.com/

When I run an OpenStudio workflow the in.json is not produced in the run directory, however, upon running the .idf file in the run directory with EPlaunch the in.json file is produced.

The Output:JSON object is present in both in the .osm and idf and is set to Yes, so I would expect that the in.json is produced in the openstudio workflow.

I also tried the debug flag of the OpenStudio CLI to no avail.

I am unable to determine why this is happening.

OpenStudio version is 3.9.0 if that is helpful

Any insights would be appreciated!

edit retag flag offensive close merge delete

Comments

Do you mean a in.epJSON file ?

Denis Bourgeois ( 2024-12-20 13:53:29 -0600 )edit

@Denis Bourgeois no I mean the "in.json"

antonszilasi ( 2024-12-20 14:23:22 -0600 )edit

Can you link to an example in.json? I’m also not sure what you are referring to.

shorowit ( 2024-12-20 19:43:06 -0600 )edit

@shorowit unfortunately I cant find a reference to this file in the EnergyPlus input output reference

I've created a share directory with a file in it here

antonszilasi ( 2024-12-23 09:50:32 -0600 )edit

I see. Usually EnergyPlus output files are "eplusout.xxx" not "in.xxx". But yes, that JSON file is the output you get from the Output:JSON object. I don't know why you wouldn't get it when you run OpenStudio CLI, I definitely have examples where we do.

shorowit ( 2024-12-23 13:31:45 -0600 )edit

add a comment

If your IDF is named "in.idf", then EP-Launch will create the JSON output file named "in.json". Running an OS workflow without specifying output file names may instead create the same JSON output file with a different name -- like "eplusout.json".