First time here? Check out the Help page!
2021-11-22 14:22:43 -0500 | commented answer | No .csv and .eso output file from simulation If you select "Yes" for CSV in OutputControl:Files, it will use the native CSV output in EnergyPlus. You can still use R |
2021-11-22 09:03:41 -0500 | commented answer | No .csv and .eso output file from simulation If you select "Yes" for CSV in OutputControl:Files, it will use the native CSV output in EnergyPlus. You can still use R |
2021-09-28 16:36:48 -0500 | answered a question | GPU specs to speed up PixelCounting The GPU accelerated PixelCounting method is most useful for models with large number of exterior solar shading surfaces |
2021-09-03 12:15:38 -0500 | received badge | ● Rapid Responder (source) |
2021-09-03 12:15:38 -0500 | answered a question | ReadVarsEso message If you have all OutputControl:Files set to No then EnergyPlus will not output a MTR file nor ESO file. The ESO file must |
2020-08-28 06:46:11 -0500 | commented answer | Modifying the idd in E+ is not recognized IdfEditor still reads the IDD so you will see your changes there, however, EnergyPlus does NOT read IDD or epJSON Schema |
2020-01-21 08:21:52 -0500 | commented question | EnergyPlus : json.exception.type_error.305 To upload an IDF file here you need to change the file extension to .txt You can also submit a ticket through EnergyPlus |
2020-01-19 13:23:47 -0500 | commented question | EnergyPlus : json.exception.type_error.305 Can you provide more details please? What version of EnergyPlus? Can you post a snippet from the error file around this |
2019-10-14 16:23:30 -0500 | answered a question | idf_max_fields in json, how it's calculated? The idf_max_fields, idf_max_extensible_fields, and idf_order fields are used internally in EnergyPlus when an IDF is aut |
2019-02-24 12:53:13 -0500 | commented answer | Program exited before simulations began There were a couple bugs in the InputProcessor in V9.0.0, which got addressed for V9.1.0 coming out next month. These ki |
2019-02-20 13:34:11 -0500 | answered a question | Missing required property 'fenestration_surface_name' You have a blank Fenestration Surface Name in the extensible list at the end of your WindowShadingControl with a name Pe |
2019-02-11 10:49:07 -0500 | commented answer | Error parsing "ThermostatSetpoint:SingleCooling" EnergyPlus can handle UTF-8 input, however, there were a couple bugs which prevented EnergyPlus from parsing it correctl |
2019-02-11 10:48:53 -0500 | commented answer | Error parsing "ThermostatSetpoint:SingleCooling" EnergyPlus can handle UTF-8 input, however, there were a couple bugs which prevented EnergyPlus from parsing it correctl |
2019-02-11 09:46:06 -0500 | answered a question | customized Energy+.schema.epJSON Since the Energy+.schema.epJSON is generated directly from the IDD then compiled into the executable, it is not possible |
2018-10-16 08:05:44 -0500 | commented answer | Why does running EnergyPlus with an old IDD no longer fail? I want to add that ExpandObjects still uses the IDD at runtime when run from the command line. However, the main EnergyP |
2018-09-17 11:57:12 -0500 | commented answer | "Error parsing "Schedule:File". Error in following line" in E+ 8.9 Both of these suggestions should avoid the input parser bug and should be used as a workaround for EnergyPlus 8.9. |
2018-09-17 11:53:21 -0500 | edited answer | "Error parsing "Schedule:File". Error in following line" in E+ 8.9 Without seeing the IDF file, you have a stray comma, semicolon, or newline. In fact, it looks like the parser might be |
2018-09-17 07:35:27 -0500 | answered a question | "Error parsing "Schedule:File". Error in following line" in E+ 8.9 Without seeing the IDF file, you have a stray comma, semicolon, or newline. In fact, it looks like the parser might be |
2017-10-30 22:13:23 -0500 | commented answer | rpict can't find rayinit.cal I would suggest adding . after $PATH instead of at the beginning as noted in this stackexchange post. Adding . to your p |
2017-10-22 13:36:13 -0500 | edited answer | compile EnergyPlus and Radiance for AVX See my comment in this question. Basically you need to use -march=corei7-avx (-march=sandybridge in GCC4.9+), -march=cor |
2017-10-22 13:34:04 -0500 | answered a question | compile EnergyPlus and Radiance for AVX See my comment in this question. Basically you need to use -march=corei7-avx (-march=sandybridge in GCC4.9+), -march=cor |
2017-10-17 14:00:53 -0500 | edited answer | Concurrent EnergyPlus simulations cause processor bottleneck!?! What is interesting is that you saw linear scaling on the Azure cloud instance (which likely use Intel processors) but n |
2017-10-17 13:57:35 -0500 | answered a question | Concurrent EnergyPlus simulations cause processor bottleneck!?! What is interesting is that you saw linear scaling on the Azure cloud instance but not with the AMD (I assume Ryzen 7 17 |
2017-09-01 12:56:23 -0500 | commented answer | openstudio 2.2.0 vs. 1.14.0 airloop @Julien Marrec It is a bug, those fields shouldn't be exposed in the GUI and needs to be updated in the OpenStudioPolicy |
2016-02-19 09:57:27 -0500 | answered a question | I can't get a Service Hot Water Plant Loop to Run. I bet this is the same bug as this (closed) issue. I would suggest updating to OpenStudio 1.10.0 to see if this fixes your problem. If it does not then there is another potential bug. |
2016-01-26 08:07:25 -0500 | commented answer | Is there an easy way to show what an OpenStudio field will accept? It seems like the more consistent API naming convention is fooValues(). Also it appears that OutputVariable hasn't implemented it fully. If you look at SimulationControl, OuputVariable should call the |
2016-01-22 21:35:48 -0500 | answered a question | Can I import/require OpenStudio SDK (Ruby bindings) into IRB? As Kyle mentioned, there is a way to customize the irb startup configuration. You have to do the following (assuming Mac or Linux): If Then inside or what I have in my This will automatically load completion and openstudio everytime you call |
2016-01-13 08:40:14 -0500 | answered a question | Can someone help me with an FArray1.hh error when compiling E+ on linux? FArray1 is a container class that holds, in this case, strings. Basically you get this assertion when you have a Debug build and you try to access an index outside the bounds of the array. For example, if you have nothing in your Array but you try to access it with fooArray( 1 ), it will throw this assertion because there is nothing at index 1. The FArray, and other Array classes, are emulation classes of Fortran's Arrays. The biggest important fact about this is that Fortran is 1-based indexing versus 0-based indexing for C++ native containers (vector, list, etc). Regarding a debugger on Linux, I would use GDB if you are familiar with command line debugging. Otherwise, I would suggest using JetBrains CLion IDE, which will help you compile EnergyPlus as well as being able to run an interactive debugger and set breakpoints. I find it very helpful and it works well. You have to pay for the IDE but as a student you can get access to it (and all of JetBrains' other IDEs) for free. I also notice from your error message it looks like you are using the runenergyplus script. I would suggest to use the command line interface native in EnergyPlus now instead of that script. Just call |
2016-01-11 14:37:32 -0500 | commented answer | Difficulty running EnergyPlus 8.4. bundled with OpenStudio 1.10. Well if you want to avoid all of that AND don't want to install separate installation of EnergyPlus then the only other option is to install OpenStudio to a different location than "Program Files". |
2016-01-11 07:28:28 -0500 | answered a question | Difficulty running EnergyPlus 8.4. bundled with OpenStudio 1.10. The error message is pretty straightforward and explains the issue well in my opinion. Since OpenStudio is installed in Another, probably better option is to change the permissions of the EnergyPlusV8-4-0 folder installed by OpenStudio. With this option, you can keep the OpenStudio installed EnergyPlus but EP-Launch and the other utilities should work when called directly. |
2016-01-11 07:16:25 -0500 | answered a question | Is there a fix or workaround for El Capitan breaking EnergyPlus? Another workaround is to use the Command Line Interface (CLI), present since EnergyPlus 8.3. This is also the preferred method to invoke EnergyPlus. To see all the command line options run For a typical simulation:
I have also created an EnergyPlus issue. |
2016-01-07 14:07:27 -0500 | commented answer | How to model a refrigerated warehouse in OpenStudio? You will also need to add the AirChiller to a Refrigeration System. |
2015-11-17 19:09:46 -0500 | answered a question | Regular Expressions to filter Output:Variable No this is not possible at this point, but it is a great User Voice suggestion. Thanks to @Eric Ringold for finding the spot, you can see in the source code that it only accepts the variable name or "*". That said, I think adding a true wildcard or regular expression looks possible (on the surface). So add this as a suggestion on User Voice. |
2015-11-13 09:55:47 -0500 | commented answer | openstudio.energyplus.ForwardTranslator: OS_ProgramControl is not currently translated @macumber The code for multi-threading is no longer in EnergyPlus (since 8.x, I forget). So while EnergyPlus might accept this input, it does not do anything. |
2015-11-11 14:22:52 -0500 | commented answer | How to set up Visual Studio to use C# bindings Did you include both |
2015-11-11 14:15:28 -0500 | commented question | How to set up Visual Studio to use C# bindings @pflaumingo Visual Studio 2015 should be okay when using the C# bindings, but it does not work when compiling OpenStudio itself. I just tested with OpenStudio 1.9.0, Visual Studio 2015 Enterprise, and the code (and instructions) from here, and it all works. I don't know what to say other than follow my instructions in that other post and if that still fails to maybe post example code. |
2015-10-14 09:30:29 -0500 | answered a question | Csharp for OpenStudio Does this answer address your question on how to get the C# DLLs to work in Visual Studio? UPDATE: I tested creating a new Model then saving it and it works for me. Make sure you follow the instructions in the linked answer completely. Also, make sure the |
2015-09-27 19:57:34 -0500 | answered a question | EnergyPlus models/testmodels I second the use of Eppy, which is in Python. I would also recommend OpenStudio, if you want to start using that ecosystem. This kind of workflow is precisely what Measures (which are in Ruby) helps accomplish. You would basically have a Measure for 2. and 3. where the Measure changes the baseline model to have HVAC 1 or HVAC 2. Thus if you change the baseline model, the measure should work exactly the same (if written well). I think without some form of scripting, this is an exercise in patience and attention to details. I would highly recommend looking into a scripting option. |
2015-09-15 16:42:09 -0500 | received badge | ● Nice Answer (source) |
2015-09-15 12:47:41 -0500 | answered a question | "Reading" .osm files You can read an OSM file similar to an IDF file. The OpenStudio Model mirrors EnergyPlus input objects fairly closely. One of the biggest differences is the "long string of {alphanumeric-string}". These are UUIDs which allow each object to be universally unique. In EnergyPlus, the object's name must be unique among all similar types of objects. OpenStudio takes this further and makes all objects universally unique through the UUID. This is advantageous when you bring objects from another model into your model through In EnergyPlus you can reference other objects within a parent object, for example a unitary system references a heating coil and cooling coil. In EnergyPlus, you put the name of the child object in the parent object field. While in OpenStudio, you put the child UUID, or handle, in the parent object field. Unlike eQuest and EnergyPlus, manipulating the OSM file directly is usually fraught with danger. Any time you create a new object you need to generate a new UUID and it must be universally unique otherwise bad and undefined things can happen. What this means in practice is that you should use the OpenStudio App, plugin, measures, or API bindings to interact with your OpenStudio model. These approaches make sure the model is generated correctly as well as provide helpful abstractions over the more tedious parts of EnergyPlus (connecting nodes in HVAC systems for example). I would advise against "working/operating only on idf files and import/export these as needed" IF you are wanting to use these within OpenStudio. OpenStudio does not import all EnergyPlus objects, especially HVAC systems. It is best to stay within OpenStudio if you want to use OpenStudio. |
2015-09-09 09:05:42 -0500 | answered a question | Is there an easy way to show what an OpenStudio field will accept? You can call OpenStudio::Model::SimulationControl::validSolarDistributionValues(). It will return a list of valid values. Usually for fields that accept a range of acceptable values, there will be a |
2015-09-07 19:32:54 -0500 | commented question | Why is my OpenStudio with Python bindings build not working? |
2015-09-06 13:53:09 -0500 | commented question | Why is my OpenStudio with Python bindings build not working? @Jamie Bull I spent many (many) hours earlier this week trying to get a working build as well. I had a working build (to generate the python bindings) before, but I think when I upgraded to Visual Studio 2015 it broke my build for some reason. I would try to build with Visual Studio 2013. I will keep trying to troubleshoot the VS2015 builds. |
2015-08-14 18:05:02 -0500 | answered a question | BUG Report in Air Terminal Thank you @Pithon. I looked at your OSM files and this is definitely a bug. I have filed a GitHub issue here. You can workaround this temporarily by opening your bug report OSM in a text editor and manually deleting these lines... from any |
2015-08-14 10:22:54 -0500 | answered a question | What could cause a measure to run fine in Apply Now but fail in PAT? Looking at the error log, it seems like the coolingCapacityFunctionOfTemperature() curve on a ChillerElectricEIR object is deleted before the ChillerElectricEIR. What happens is that when ChillerElectricEIR is deleted it tries to delete it's children (curves) and the way the coolingCapacityFunctionOfTemperature() function is written, if it doesn't find its associated curve it will crash. A common cause of this issue (and one i've had happen to me as well) is if you share curves between objects. You should never use a curve on more than one object or even for different fields in the same object. Curves do not behave like Schedules in OpenStudio. This will for sure cause the above error. What happens is that an object will delete itself and all curves, regardless if that curve is used elsewhere. Then when you go to delete a different object that was using that same curve, it tries to delete that curve again but it is no longer valid and will crash OpenStudio. If you are using the GUI only, this kind of error should never happen and is definitely a bug if it does. If you are using measures and the API then it is possible and likely for this crash to happen if you are not careful. If you are not sharing curves between objects then something else in your measure is deleting the curve before the ChillerElectricEIR is deleted. Without seeing the measure it is hard to know for sure. |
2015-08-13 09:52:10 -0500 | commented answer | Any experience with the following Openstudio crash? "An unhandled exception has occurred. Access violation - no RTTI data!" I just want to mention, what I wrote for the workaround for @Julien Marrec is specific to his model. The general principle is the same for all models though. Make sure to clean up any malformed |