edia and technology. Under the umbrella of MASSv.1.0 Robots and Cyborgs International Workshop and will be supported by a series of lectures. The workshop will integrate the use of a robotic fabrication with Virtual Reality. …
edia and technology. Under the umbrella of MASSv.1.0 Robots and Cyborgs International Workshop and will be supported by a series of lectures. The workshop will integrate the use of a robotic fabrication with Virtual Reality.
…
Mmm really nice post. Usually light electronic Trip Hop, or spanish Hip-Hop.
Portishead
Radiohead
Massive Attack
Propellerhead
SFDK
Juaninacka
Tote King
Best Regards ;)
to select a period of time across the year, for example, every hour from January 1 to June 30.
I currently use DOY/HOY to assign the analysis period (basically I want to run 8760 hours), and connect its HOY to DAY_MONTH_HOUR_CALCULATOR. Then, connect it to CB sky. But, there are several warnings pop-up on the component "DOY/HOY", says Feb. has 28 days, the date is corrected by Ladybug, and as well as other months less than 31 days. After the HOY is connected to the "DAY_MONTH_HOUR_CALCULATOR", the warnings are gone, and the lines become green. However, when I connect the "DAY_MONTH_HOUR_CALCULATOR" to CB sky, the output of "sky file pate" turns orange again. This causes the repetition of the last day of those months less than 31 days.
(I attach a picture for your information)
Does any of you know how to solve this problem? And what is the best way to run annual hourly (8760 hours) with CB sky?
Many thanks in advance!!
Wenhsin…
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.…
in reality gives meshes out instead. There also seems to be an issue in the component, as in instead of giving the shadow region ( mesh) it is giving a mesh spanning the entire site. however if I just use 2 blocks out of the 28 blocks I am getting accurate result. please help.…
he canvas redrawing and the Rhino viewport redrawing take some time as well (on my system 6 ms for the empty Gh canvas and 28 ms for the empty Rhino viewport). No timer can avoid that, to my knowledge. The trampoline computes timing after the solution is complete. This means that one cycle is: solution completed + drawn + user specified interval.
Hope that this helps to get started,
- Giulio________________giulio@mcneel.com…
this common installation problem please find a tested remedy shared by one of the group members:
Comment by Iman Sheikhansari on August 26, 2019 at 8:33amDelete Comment
HiIf you are encountering a problem with rhino 6 versions don't worryFollow these steps.1. Download SYNTACTIC from https://sites.google.com/site/pirouznourian/syntactic-design2. Install it and go to the installation folder, Drag & drop SYNTACTIC(green one) over your grasshopper canvas.3. Close your rhino and reopen it. 4. Type GrasshopperDeveloperSettings5. Tick the Memory load *.GHA assemblies using COFF byte arrays option6. Run grasshopper and enjoy plugin
I hope this helps,
Best regards,
Pirouz
…
s helped in the past...but again I must be missing something simple.
here is the code and error--attached are the def and (.3DM) file:
----------------------------------------------------------------------
import rhinoscriptsyntax as rs
import ghpythonlib.components as ghcomp
#print UV
pc = []
maxVecs = []
revVec = []
movedPts = []
pc = ghcomp.PrincipalCurvature(surface, UV)
maxVecs = pc[4]
frames = pc[0]
for vector in maxVecs:
#print vector
tempVec = rs.VectorReverse(vector)
revVec.append(tempVec)
for i in range(len(frames)):
#print frames[i]
print revVec[i]
tempPt = rs.MoveObject(frames[i],revVec[i])
#movedPts.append(tempPt)
vectors = revVec
--------------------------------------------------------------
Runtime error (TypeErrorException): Parameter must be a Guid or string representing a Guid
Traceback:
line 468, in coerceguid, "C:\Users\Aaron\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rhinoscript\utility.py"
line 1081, in TransformObjects, "C:\Users\Aaron\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rhinoscript\object.py"
line 396, in MoveObjects, "C:\Users\Aaron\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rhinoscript\object.py"
line 382, in MoveObject, "C:\Users\Aaron\AppData\Roaming\McNeel\Rhinoceros\5.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rhinoscript\object.py"
line 28, in script
Any help with understanding what's going on would be really helpful.
aaron…