Julien Marrec's profile - activity

This is likely the same issue as reported here: openstudiocoalition/OpenStudioApplication#722 and due to this SDK issue:

This is likely the same issue as reported here: openstudiocoalition/OpenStudioApplication#722 and due to this SDK issue:

This is likely the same issue as reported here: openstudiocoalition/OpenStudioApplication#722

This is likely the same issue as reported here: https://github.com/openstudiocoalition/OpenStudioApplication/issues/722

What Denis said. When you look at the SDK documentation for an object, you can click the button "List of all members"

What Denis said. When you look at the SDK documentation for an object, you can click the button "List of all members"

What calling point are you using (EMS:ProgramCallingManager). Also, use Output:EnergyManagementSystem with the field Ene

I'm using OpenStudio to simulate with EnergyPlus. I want to get a csv file out of it in order to do some post-processing.

As stated in the thread Getting csv from sql, one way to get the csv is to re-run the IDF file generated by OpenStudio through the EP-Launch program. But that would require running the simulation a second time, which I want to avoid.

OpenStudio does save the .eso file, and I can process it just fine using ReadVarsESO that comes with EnergyPlus. The only problem is that I'm getting this message

 ReadVarsESO program starting.
 too many variables requested, will go with first          255

Now, in EP-launch, if you go to Options, then "Miscellaneous", you can tick an option "Allow more than 250 columns", and you'll end up with a csv that has all the reporting variables, even if more than 250 or 255.

So I'm guessing there's a way to call ReadVarsEso with some kind of parameter that tells it to ignore the columns limit.

How can you run the ReadVarsESO without the 255 columns limit?

Not enough information to reproduce/help. Also, it looks like a warning, and not an error. Seems to fallback to using th

If I understand correctly, your problem is with this EMS Sensor: EnergyManagementSystem:Sensor, RCan,

If I understand correctly, your problem is with this EMS Sensor: EnergyManagementSystem:Sensor, RCan,

EMS Sensor Unique Key Name not found. Hello, we are working on our graduation project. I want to obtain the transpiratio

https://unmethours.com/question/99516/ems-sensor-unique-key-name-not-found/

Energyplus error message i usually use Openstudio to get the data i need but i'm starting to use Energyplus but i keep g

Answering generally: the easiest to checkout the repository, and point your "My measures" folder to the measures/ direct

Add meassure from github to Openstudio How you can add a meassure from github to my openstudio model? This is the meass

Could you try the same in 3.8.0 please? I don't feel like investigating something that might have already been fixed (co

https://bcl.nrel.gov/ is up today at least.

These are still not the EnergyManagementSystem:Program and EnergyManagementSystem:ProgramCallingManager, both objects ar

Hard to say given how little information you gave us as to how you're trying to connect the FMU. That socket.cfg is a fi

How I can solve socket.cfg in energyplus FMU Hi there, I am trying to work with energyplus FMU for a simple simulation.

In the OpenStudioApplication, you can access the companion directory from the "Run" Tab, there is "Show Simulation" butt

In the OpenStudioApplication, you can access the companion directory from the "Run" Tab, there is "Show Simulation" butt

In the OpenStudioApplication, you can access the companion directory from the "Run" Tab, there is "Show Simulation" butt

None of these are hard errors, and can probably be ignored. Your issue is something else. If it fails to simulate in E+,

These are still not the EnergyManagementSystem:Program and EnergyManagementSystem:ProgramCallingManager, both objects ar

Fixed in OS SDK 3.8.0 via https://github.com/NREL/OpenStudio/pull/5170

Fixed in 3.8.0 FYI.

Where is the EMS:Program and EMS:ProgramCallingManager?

ScheduleRuleset is an OpenStudio specific object provided for convenience. It has: A default ScheduleDay Potential s

ScheduleRuleset is an OpenStudio specific object provided for convenience. It has: A default ScheduleDay Potential s

This is just the wrong EMS calling point, You're using callback_end_zone_timestep_after_zone_reporting. Please refer to

@BrianLBall does that ring a bell to you please?

I find it strange that your project (apparently named debugger3 and placed at C:\ParametricAnalysisTool-3.6.1\pat\debugg

Can you open cmd.exe (or powershell), and run that openstudio_meta start_local command with a --verbose adde din between

Can you open cmd.exe (or powershell), and run that openstudio_meta start_local command with a --verbose adde din between

Running PAT on VirtualBox VM - server won't launch Hello! I have a goal to install OpenStudio Application and Parametri

See: climate_zone = czs.climateZones[0] "#{climate_zone.institution} 169-#{climate_zone.year}-#{climate_zone.value}"

climate_zone = czs.climateZones[0] "#{climate_zone.institution} 169-#{climate_zone.year}-#{climate_zone.value}" =>

climate_zone = czs.climateZones[0] "#{climate_zone.institution} 169-#{climate_zone.year}-#{climate_zone.value}" =>

Adjust the climate zone tags like I said. The correct value is demonstrated below m = OpenStudio::Model::Model.new czs

Adjust the climate zone tags like I said. The correct value is demonstrated below m = OpenStudio::Model::Model.new

It's expecting ASHRAE 169-2013-3C not ASHRAE 169-2006-ASHRAE 169-2013-3C. https://github.com/NREL/openstudio-standards

It fails here: https://github.com/NREL/openstudio-standards/blob/18e3a888f58191a8dcd75a9749f639a4619340b6/lib/openstudio

Either use PAT, or write your own. You can load the sqlFile (either in Ruby/Python directly, or via OpenStudio::SqlFile