e structure systems. It presents an algorithmic process where the initial generative rule is based on the growth of Cellular Automata (CA). Digital Fabrication techniques will be used for prototyping. Theoretical lectures about Cellular Automata, Generative design and fabrication techniques will be presented .
Duration : 21 June. – 28 June. 2013 from 10 am to 6 pm Location : ENCODE Studio Address: 2 Wataneya buildings , 14 May Bridge , Smouha , Floor 1 , Apartment 106 Tel: 03-3823637 Mob: 0100-9879995 Email: encodestudio.mail@gmail.com Website: www.encodestudio.net for more information and registration please fill the following form : https://docs.google.com/forms/d/1FC9-CIDsNuzMkmu3Rubj45_7zTBb6YB3OfYnEA9xOMk/viewform?edit_requested=true Attendance Confirmation email will be sent to confirm availability…
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.…
思った感じになりません。
balls の代わりにplanarカーブを直接入れてみましたがエラーが出ます。
ファンクションにしてみたところ、forループので作った数値が反映されていません。
ファンクションのインスタンス?を出力していないと思い上記のようにしましたがエラーが出てしまいます。
以上の事から自分の認識が正しいのかよくわからなくなりました・・・
python自体の深いところをわかっているわけではないので余計こんがらがりました。
そこで、for b in ballsはどのような条件または使い方であれば使えるのでしょうか?
そして、上記のように別のオブジェクトに対しての使い方はどのようにすればできるのでしょうか?
2:同じファンクション内のdist = rs.Distance(self.pos,b.pos)についてですが
この文章も for b in balls によってbはBallのインスタンスであると定義?されたためb.posがbの位置であると分かるのでしょうか?
pythonは定義しなくても動いてしまうのでどのような時に使えるのか文章見ただけではよくわかりません・・・
大変細かいことかもしれませんが、よりpythonをしっかりと理解するためにも、どなたかわかる方ご教授いただけると幸いです。…
heating? Or cooling?)
What if you have 20C? You need to heat to 24-26?
What if you have 28? Then you cool to 24-26?
Something is missing here ...
Or am i wrong? (In this case i don't understand the logic).
Besides that, you are simulating 3 zones instead of 1. Your conncetions of all the HB_setEPZoneSchedules to the HB_setEPIdealAir is causing this. Messy ... a little bit.
-A.…
which doesn't exist in the actual problem spec. If galapagos is allowed to change the column position in all possible directions, it is less likely to get stuck in some local optimum.
Let's assume that (all other things being equal) column 20 would yield the best possible answer. The current state of the system though is at column 26, which is pretty good too, just not as good. Galapagos is more likely to 'mutate' the state a little bit instead of a lot, so it'll explore the columns near 26. However 20 isn't near 26 at all, only 25 and 27 are nearby, and maybe 24 and 28. But they'll all worse answers, so after sampling in those directions GP will abandon that as fruitless.
If however you specify the columns using two variables, then the columns near 26 are 20, 25, 27 and 32. That's a far richer space to explore which much better approximates the real problem.…
.components as ghimport karamba
I have copied all the folder named '64bit' in grasshopper library folder (items are not in a sub-folder). The karamba.py gives me back an in-script error, i.e.
Runtime error (ImportException): No module named _karambaTraceback:line 20, in swig_import_helper, "C:\Users\Claudio\AppData\Roaming\Grasshopper\Libraries\karamba.py"line 28, in <module>, "C:\Users\Claudio\AppData\Roaming\Grasshopper\Libraries\karamba.py"line 2, in script
Just wondering if I could have an help about this. I tried the IronPython example, but it keeps saying that the karamba.gha does not exist in my plugin folder (but it's there). This occurs on line 3 of your example on the operation clr.AddReferenceToFileAndPath(*the path it finds*)
Many thanks
Claudio…