Julien Marrec's profile - activity

Without your test script or more info, it's hard to tell whether you have incorrectly configured the path to the Dymola

The OpenStudio gbxml forward translator at least writes both. The RectangularGeometry defines a kind of an area-equiva

I agree with what Denis and Aaron said. The likely cause is the fact that the building has less ability to cool itself d

The installation steps are described on: https://github.com/openstudiocoalition/openstudio-sketchup-plugin/wiki/OpenStud

You can use the python multiprocessing module to run multiple simulations in parallel. A short example can be found here

Posted as an issue here: https://github.com/NREL/EnergyPlus/issues/9798 With a Pull request fixing it at https://github

I think you are right. That said, this type of things should be best posted as an issue directly at https://github.com/N

same in openstudio. You can even do that in the OpenStudioApplication.

I've created an osm file from Honeybee, and later on I realized I forgot a detached space. I created a second .osm file for this space.

What's the best way to integrate my second .osm file in the first one, without duplicating schedules and constructions etc.? I just want the geometry.

For a crude way to do it, schedule your infiltration object. For example, you can use a SpaceInfiltrationDesignFlowRat

I just added an AirLoopHVAC with an Outdoor Air System and an AirLoopHVAC:UnitarySystem .

The AirLoopHVAC:UnitarySystem itself contains a Coil:Cooling:WaterToAirHeatPump:EquationFit, aCoil:Heating:WaterToAirHeatPump:EquationFit and a supplemental heating Coil:Heating:Water as well as a Fan:VariableVolume, and it is set to Control Type Load with one of the two zones it serves (a lobby and a vestibule) as a control zone.

My simulation time completely bloated. It went 08min50 to 1h35min (and 15 minutes later it's still writing the SQL file...), and I'm getting convergence issues during the warmup. I didn't change anything else.

Is there anything I can do to avoid having such a long simulation time?

Any workarounds I could use such as wrapping a single coil in a dedicted unitary system set to Setpoint or something? This is making my model completely useless.

Can you include the IDF snippet for the specific FenestrationSurface:Detailed that is throwing the error please?

Unless you define soil properties, and/or Site:GroundTemperature:XXX objects (eg Site:GroundTemperature:Surface) it'll

Make a concrete floor then?

Please remember to mark an answer as Accepted (green check mark below the up/down vote buttons) so the thread is marked

Are you connected to the internet? If so, it's a firewall issue, contact your IT department? What version of the OpenStu

Do you have an A/C system in your model? Is it running as expected and meeting setpoint? Have you added some infiltratio

As Denis said, generally. For your specific application, which is modeling one room as part of a larger building, the e

thanks for opening 4715, really helpful!

If the correct behavior is to NOT generate an UnitarySystemPerformance:Multispeed when you use a Variable speed coils (t

Please mark the answer as accepted so the thread is marked resolved (green check mark below the Up/Down vote buttons). T

My understanding is that the Number of Speeds and UnitarySystemPerformance:Multispeed is specifically for multispeed coi

E+ doesn't run because your macOS system version is too old to support the std::filesystem from C++17. What version are

On the Run Tab, click the "Verbose Output" checkbox at the top and try to see if you can get more information. Also, tr

I would suggest you start using IPython (= a better interactive prompt) or a Jupyter notebook (which uses IPython, and a

Have you seen my answer below?

Glad you got it sorted.

cf image I added in the two years old answer above (The question was answered (with what limited information was given).

cf image I added in the two years old answer above.

You have a few coils such as Coil:Cooling:Water and Coil:Heating:Water somewhere in your model that are likely connected

You seem to assume there must be a bug, but there are none. The AirTerminalSingleDuctVAVReheat is the air side component

This looks like an issue in the code for the reporting script. This is typically something that happens when you try to

Yeah so the the Key has to be the object's name, not the Zone it's in.

I suggest having Output:VariableDictionary in the IDF format so you can copy from the .RDD to your IDF file without erro

I suggest having Output:VariableDictionary in the IDF format so you can copy to your IDF file without error: Output:Var

Can you post the actual IDF snippet for your Output:Variable? I bet that's the issue.

Output Variable associated with ZoneHVAC:Baseboard:Convective:Electric not working Hi, I am trying to setup a Baseboard

Output Variable associated with ZoneHVAC:Baseboard:Convective:Electric not working Hi, I am trying to setup a Baseboard

A couple of places to look at: E+ internal API tests: EnergyPlustst/EnergyPlus/api I have an example notebook: jmarrec

A couple of places to look at: https://github.com/NREL/EnergyPlus/tree/develop/tst/EnergyPlus/api https://github.com/j

Note that this will be available in the upcoming release of OpenStudio SDK (the one after 3.4.0). Please refer to OpenSt

Note that this will be available in the upcoming release of OpenStudio SDK (the one after 3.4.0). Please refer to https:

Read the documentation: https://nrel.github.io/EnergyPlus/api/python/datatransfer.html#datatransfer.DataExchange.get_tre