RS method of RhinoMembrane is one of the base theories and the new release will be available after i showcase it in Munich at the structural membranes conference on 9 october , keep in touch I will let you get a trial.
gerry
…
Added by Gerry D'Anza at 2:11pm on September 27, 2013
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…
and in-between 5 & 9) then what happens. There are just too many unknowns for this to be solved with such a simple explanation. Your problem is easy for a brain to know, but difficult for a computer to understand. Think about a CAPTCHA, i would say its the equivalent problem: we can decipher what one says almost immediately, but a computer can not.
http://en.wikipedia.org/wiki/CAPTCHA
Or have i not under stood you correctly?
(Also, just to start with the problems that need to be addressed, lets go back to why 1 and 2 are not connected? 2 & 3 are, 3 & 4 are etc. Its already inconsistent. You need to define rules. You've mentioned nothing about proximity, which as far as i can decipher, seems to be a driving factor behind what you have pointed out. Its all very confused to be honest)…
s
(distance from Spine to Profile)
4) Create Circles at each floor
5) Rotate Each Floor by twisted amount
(according to height of floor)
6) Divide each floor by number of Flutes
7) Flip Matrix of Flute Points (version 0.7)
(if using v0.6 then search flip matrix on site for method)
(Rows to Columns)
8) Interpolate Curve through Flute Points
9) Mirror Flute Curves
10) Create display grid
11) Make a vector 2Pt from the floor centre
to the corresponding display point…
ading RAD default materials...9 RAD materials are loaded1. 2. Downloading OpenStudioMasterTemplate.idf to C:\Users\Wesley\AppData\Roaming\Ladybug\3. Download failed!!! You need OpenStudioMasterTemplate.idf to use honeybee.Please check your internet connection, and try again!4. Download failed!!! You need OpenStudioMasterTemplate.idf to use honeybee.Please check your internet connection, and try again!5. Hooohooho...Flying!!Vviiiiiiizzz...…
, this (or that). That's the difference between 10 minutes of coding VS 100++.
Anyway ... provide the dataset that caused the issue.
In the mean time get the trad update that proves that the pink color is good for the Pink Planet (after Utopia turn left Math.PI/666.0).
Other type of (rather expected) oops moments:
1. Dupes, 2.Closable (but not closed) "final" (see code) profiles, 3. Shortage of cigars (critical), 4."Unexpected" polylines, 5. Loft failure(s), 6. Not "matching" final profiles (N of nodes) ... 666. ...
…
er.
2. Write importer VB script to parse dat files and create Grasshopper polylines.
3. Manually remove country border curves from coastal curves.
4. Manually join remaining curves into as many closed loops as possible.
5. Remove short polylines and short segments from long polylines.
6. Map polylines onto sphere.
7. Project spherical polylines onto manually created icosahedron using a VB script.
8. Split polylines along facet boundaries and create groups of all polyline segments that fall within a single triangle.
9. Manually unfold the icosahedron.…
Added by David Rutten at 5:11pm on February 11, 2012
ere a way to set this up in a way that lets say when there are 28 it will go for one of 4, 7 or 14 and if it is a primer number it will exclude enough number of boats to obtain the closest suitable number - lets say there are 29 boats but it will only show 28 and go back to selecting 4,7 or 14.…
Added by Levent Ozruh at 10:40am on October 14, 2014
NONE, in SIZING:PARAMETERS". I'm not sure of where to start in troubleshooting this. I've attached the file.
Thank you,
See the errors and warnings below:
{0;0;0}
0. Current document units is in Meters
1. Conversion to Meters will be applied = 1.000
2. [1 of 8] Writing simulation parameters...
3. [2 of 8] Writing context surfaces...
4. [2 of 8] Writing context surfaces...
5. [3 of 8] Writing geometry...
6. [4 of 8] Writing Electric Load Center - Generator specifications ...
7. [5 of 8] Writing materials and constructions...
8. [6 of 8] Writing schedules...
9. [7 of 8] Writing loads and ideal air system...
10. [8 of 8] Writing outputs...
11. ...
... idf file is successfully written to : R:\Green\SuRG\Building_Performance_Analysis\2016_analysis_studies\Energy_Analysis_Comparison\Honeybee_+_Ladybug\tutorial01\EnergyPlus\tutorial01.idf
12.
13. Analysis is running!...
14. ...
...
Done! Read below for errors and warnings:
15.
16. Program Version,EnergyPlus, Version 8.5.0-c87e61b44b, YMD=2016.10.31 11:39,IDD_Version 8.5.0
17.
18. ************* IDF Context for following error/warning message:
19.
20. ************* Note -- lines truncated at 300 characters, if necessary...
21.
22. ************* 24 Sizing:Parameters,
23.
24. ************* Only last 1 lines before error line shown.....
25.
26. ************* 25 None, !- Heating Sizing Factor
27.
28. ** Severe ** IP: IDF line~25 Invalid Number in Numeric Field#1 (Heating Sizing Factor), value=NONE, in SIZING:PARAMETERS
29.
30. ** Warning ** IP: Note -- Some missing fields have been filled with defaults. See the audit output file for details.
31.
32. ** ~~~ ** Possible Invalid Numerics or other problems
33.
34. ** Fatal ** IP: Errors occurred on processing IDF file. Preceding condition(s) cause termination.
35.
36. ...Summary of Errors that led to program termination:
37.
38. ..... Reference severe error count=1
39.
40. ..... Last severe error=IP: IDF line~
, value=NONE, in SIZING:PARAMETERS
41.
42. ************* Warning: Node connection errors not checked - most system input has not been read (see previous warning).
43.
44. ************* Fatal error -- final processing. Program exited before simulations began. See previous error messages.
45.
46. ************* EnergyPlus Warmup Error Summary. During Warmup: 0 Warning; 0 Severe Errors.
47.
48. ************* EnergyPlus Sizing Error Summary. During Sizing: 0 Warning; 0 Severe Errors.
49.
50. ************* EnergyPlus Terminated--Fatal Error Detected. 1 Warning; 1 Severe Errors; Elapsed Time=00hr 00min 9.34sec
51.…
give or take a few hundreds ).
I hear you: but you've just added 3 f#%#$g lines: Yes but it's the quality that matters (and greed).
Send the Da Morgada hot stuff ASAP to: The Lord, District 9, North Pole.…