EC
1. Between hours 1:00 to 24:002. Current document units is in Meters3. Conversion to Meters will be applied = 1.0004. [1 of 7] Writing simulation parameters...5. [2 of 6] No context surfaces...6. [3 of 6] Writing geometry...7. [4 of 6] Writing materials and constructions...8. [5 of 7] Writing schedules...9. [6 of 7] Writing loads and ideal air system...10. [7 of 7] Writing outputs...11. ...... idf file is successfully written to : c:\ladybug\Freeformtower_IDF\EnergyPlus\Freeformtower_IDF.idf12. 13. Analysis is running!...14. ......
Done! Read below for errors and warnings:
15. 16. Program Version,EnergyPlus-Windows-64 8.1.0.009, YMD=2015.04.04 23:39,IDD_Version 8.1.0.00917. 18. ************* IDF Context for following error/warning message:19. 20. ************* Note -- lines truncated at 300 characters, if necessary...21. 22. ************* 577 Zone,23. 24. ************* Only last 1 lines before error line shown.....25. 26. ************* 578 Freeformbuilding27. 28. ** Warning ** IP: IDF line~578 Comma being inserted after:" Freeformbuilding" in Object=ZONE29. 30. ** Severe ** Out of range value Numeric Field#5 (Type), value=0.00000, range={>=1 and <=1}, in ZONE=FREEFORMBUILDING31. 32. ************* IDF Context for following error/warning message:33. 34. ************* Note -- lines truncated at 300 characters, if necessary...35. 36. ************* 586 BuildingSurface:Detailed,7341.
…
cs/numpy-for-iron-python-wit... ) also fails to allow numpy import:
Numpy and Scipy are in directories here:
C:\Program Files (x86)\IronPython 2.7\Lib\site-packages\
This is all a sad joke, taking a full day so far. Rhino just sort of sucks for serious work. There's no way I can offer any Numpy/Scipy scripts to clients this way, just impossible. Rhino/Grasshopper Python should come with this stuff, dear developers, or have a simple installer that just works. It comes with math already doesn't it? So why not Numpy and Scipy for serious users?
Upon restarting Rhino, it totally changes behavior and spits out a crazy error upon importing Numpy:
Message: The type initializer for 'NumpyDotNet.NpyCoreApi' threw an exception.Traceback: line 11, in <module>, "C:\Program Files (x86)\IronPython 2.7\Lib\site-packages\numpy\core\multiarray.py" line 6, in <module>, "C:\Program Files (x86)\IronPython 2.7\Lib\site-packages\numpy\core\__init__.py" line 155, in <module>, "C:\Program Files (x86)\IronPython 2.7\Lib\site-packages\numpy\__init__.py" line 1, in <module>, "C:\Users\Nik\AppData\Local\Temp\TempScript.py"
The Grasshopper Python node editor gives the same error. Perhaps I can only import parts of Numpy using "from Numpy import XXXX"?…
Added by Nik Willmore at 3:32pm on October 11, 2015
Writing simulation parameters...3. [2 of 8] No context surfaces...4. [3 of 8] Writing geometry...5. unsupported operand type(s) for +: 'str' and 'list'6. Failed to write Pelle_aperture000 to idf file7. unsupported operand type(s) for +: 'str' and 'list'8. Failed to write Pelle_aperture001 to idf file9. unsupported operand type(s) for +: 'str' and 'list'10. Failed to write Pelle_aperture002 to idf file11. [4 of 8] Writing Electric Load Center - Generator specifications ...12. [5 of 8] Writing materials and constructions...13. [6 of 8] Writing schedules...14. [7 of 8] Writing loads and ideal air system...15. [8 of 8] Writing outputs...16. ...... idf file is successfully written to : C:\Users\Personal\Desktop\TESI\x001\THOR\EnergyPlus\THOR.idf17. 18. Set runEnergyPlus to True!
or this
0. Current document units is in Meters1. Conversion to Meters will be applied = 1.0002. [1 of 8] Writing simulation parameters...3. [2 of 8] No context surfaces...4. [3 of 8] Writing geometry...5. Runtime error (MissingMemberException): 'hb_EPFenSurface' object has no attribute 'blindsMaterial'6. Traceback:line 1567, in main, "<string>"line 2134, in script
i think that i've same problem with my windows...any suggestion???
Thanks for all…
the loops haven't even started yet. This is a one time overhead - re-starting the loops after that doesn't have this long delay until you close and re-open the file.
Second, I got some encouraging results rather quickly but then spent WAY TOO MUCH TIME trying to replace the inner loop with a "Fast Loop". These are not well behaved in the sense that they don't respond to <ESC> like the "Classic" loops do so you can't stop them; and I never got the same results as the "Classic", no matter what I tried - but ultimately, I just got too frustrated with "Fast Loop" causing Rhino/GH and my whole laptop to freeze up - VERY BAD!!!!!!!!!!
I re-wired the loops slightly so that the hour used by your 'analysisPeriod' cluster is determined by the 'D0' value inside the inner loop.
I added a "Loop On / Loop Off" switch to stop/start the looping (which was useless with "Fast Loop" - grrr....).
I 'Simplified' the 'D1' output of the inner loop and enabled 'Record data' and 'Output after the last' on the outer loop.
And I got this - four buildings over three hours takes about 20 seconds:
Eleven buildings over three hours takes about one minute.
I'm not sure what will happen when I increase the hours and number of buildings but will try it when I have more time. It might be a good idea to avoid writing to Excel inside the loops and wait for the end results before writing them to an Excel file?
There are more possibilities for re-wiring based on simplifying various outputs but I'm tired of this for now and have other things to do. The exponential slowdown you observed might be due in part to Anemone adding an extra branch path every time it loops; adding 'Simplify' might help this?
P.S. 11 buildings over 13 hours (6am to 6pm) took 5 minutes 38 seconds.…
Added by Joseph Oster at 12:54pm on January 18, 2016
of Space, 1984) and specified in (Turner A. , “Depthmap: A Program to Perform Visibility Graph Analysis, 2007), intuitively describe the difficulty of getting to other spaces from a certain space. In other words, the higher the entropy value, the more difficult it is to reach other spaces from that space and vice-versa. We compute the spatial entropy of the node as using the point depth set:
(11)
“The term is the maximum depth from vertex and is the frequency of point depth *d* from the vertex” (ibid). Technically, we compute it using the function below, which itself uses some outputs and by-products from previous calculations:
Algorithm 4: Entropy Computation
Given the graph (adjacency lists), Depths as List of List of integer, DepthMap as Dictionary of integer
Initialize Entropies as List(double)
For node as integer in range [0, |V|)
integer How_Many_of_D=0
double S_node=0
For depth as integer in range [1, Depths[node].Max()]
How_Many_of_D=DepthMap.Branch[(node,depth)].Count
double frequency= How_Many_of_D/|V|
S_node = S_node - frequency * Math.Log(frequency, 2)
Next
Entropies [node] = S_node
Next
…
rights to register the "mapwingis.ocx" file.Francesco, would you be patient just a tiny little bit, so that we could try something else? I would be grateful if you could.
1) Close Grasshopper and Rhino2) Run the Revo Uninstaller Pro and uninstall your MapWinGIS application along with removing all the leftovers from the registry.3) Restart your PC, and once it boots again, make sure that you are logged in as an Adminstrator.4) In your Start menu's search box type: "UAC", which will find your User Account Control Settings. Click on it, and a new window will open. Set the bar on the left to "Never notify".5) Turn off your Antivirus, which ever it is.6) Download the 64 bit version of v4.9.4.2 MapWinGIS.7) Right click on downloaded MapWinGIS-only-v4.9.4.2-x64.exe file, and choose "Properties". If there is "Unblock" button click on it, and then click on "OK". If there is no "Unblock" button, just click on "OK".8) Left double click on MapWinGIS-only-v4.9.4.2-x64.exe file and install it to "C:\dev\MapWinGIS" folder. Choose "Full installation" during installation process!9) In your Start menu's search box type: "CMD". Once the "Command prompt" appears do not left click on it! Instead right click on it, and choose "Run as Administrator".10) A command prompt window will open. Type the following command:
"your_regsvr32_folder_path\regsvr32.exe" /u /s c:\dev\mapwingis\mapwingis.ocx
If command does not result in an error message, then type this one afterwards:
"your_regsvr32_folder_path\regsvr32.exe" /s c:\dev\mapwingis\mapwingis.ocx
11) If no error appeared again, then open your Rhino and Grasshopper and check what Gismo_Gismo component prints from its "readMe!" output.If errors appeared, it would be nice if you could post their screenshots.…
Added by djordje to Gismo at 5:46am on March 27, 2017
and visualizing data for ENVI-Met 4 software. ENVI-met is a cutting edge software used to analyse microclimate interactions in urban environment. Tens of different analysis types can be performed on the chosen building context. From Mean radiant temperature and local Wind speed to CO2 concentration and Pollutant dispersion in the air. To generate the building context for Ladybug ENVI-met components, Antonello used Gismo:
An example similar to results in upper screenshots has been been attached below. To run it, Gismo, Ladybug and Human plugins need to be installed. To perform the ENVI-met analysis, download ENVI-met 4 Basic for free, and install it. Steps in the .gh example file have been labelled from 1 to 11. They mostly consist of just setting a boolean toggle to True. An exception to this are steps 6 (set the folder path of your ENVI-met application install folder), and 8 (running the ENVI-met simulation). Step 8 has been explained in detail in the photo attached below (step8.jpg). Special thanks to Antonello for developing and guidance on ENVI-met application and components! Post questions below if you have any issues!…
Added by djordje to Gismo at 11:30am on March 25, 2017
ries", but it could be changed in the future with nicer and more interesting names.
It's perfectly known that lot of plugins has been released to empower GH panelling capabilities, but usually lightweight and native systems could be required to accomplish specific little (or big) design tasks. In addition to this, the panelling process is a task that let the user to play and learn and practice deeply concepts about surface/meshes topology, list and data trees management, etc. So I though that this could be a perfect starting point for the "Utilities series" in c+GH.
To open this group of c+GH post I will start with something simple that everyone that have used GH has tried sooner or later in his/her learning process: how to panel a surface using standard/built-in GH components only.
Topics that could be covered (aka, problem categories):
Planar panels.
Curved panels.
Mixed solutions: curvature/distortion triggers or limits.
Given a NURBS surface, create a single panelling system that implement one of the categories described for only one kind of panel (triangular, quadrilateral, n-gon). Of course, curved panels are not compatible with triangular shapes, etc, so try to pick a compatible combination.
Further considerations:
The implemented solution should let the user to interact with every panel easily, so the proposed algorithm should track the panellization process avoiding to destroy helpful information/data structures for further modifications in the panelling system.
NURBS and mesh solutions are both allowed.
None, plugin or scripted component allowed.
The cleanest, shorter and less processing-time-expensive solution in every category will be the winner (please, consider using profiler intensively).
Deadline: May 18, 2014.
…