means Galapagos has got nothing to go on.
Your fitness value needs to reflect the fitness of the slider position. Then, Galapagos needs to be told what it is supposed to be looking for. I.e. it should try and minimize the fitness value (lower = better), maximize the fitness value (higher equals better) or optimize the fitness value (closer to X = better).
I attached two files, one extremely simple, one a bit more involved. They both solve the same problem. Be sure to have a good look at the Galapagos settings, as they differ in both files.
There's one more thing I should say. Galapagos has algorithms build in that prevent the same genome from occurring more than once in any given species. If you have an Integer slider with 11 possible settings, that means you can only have 11 unique genomes. Galapagos will exhaust this pool in half no time, after which it will seem to jump randomly back and forth, desperately trying to find another unique genome (and always failing). This is why I used floating point sliders, to increase the number of possible unique genomes.
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
Added by David Rutten at 3:52am on October 18, 2010
dd(i - 1)out_v.Add(val)out_i.Add(i) End If
eg List Length = 11, Mid = 4 and 5 (not 5 and 6).
Next time we meet I'll buy you a beer. Although I've been thinking about all the virtual beers I've been bought on here and was thinking about setting a link to a paypal account so I can start cashing in on them :))…
Added by Danny Boyes at 6:26am on September 5, 2011
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をしっかりと理解するためにも、どなたかわかる方ご教授いただけると幸いです。…
is also worth mentioning that, if you haven't used them yet, we have a few components that can help you manage and format your geometry in the way that E+ likes (including components to split building masses into core/perimeter zones and a component to ensure that there are reciprocal matching surfaces of adjacent zones). These 3 videos in the Honeybee Energy Modeling tutorial series should help you use them in your workflow:
https://www.youtube.com/watch?v=cDvBWDA0aF0&list=PLruLh1AdY-SgW4uDtNSMLeiUmA8YXEHT_&index=10
https://www.youtube.com/watch?v=DClON71RuuA&list=PLruLh1AdY-SgW4uDtNSMLeiUmA8YXEHT_&index=11
https://www.youtube.com/watch?v=nMQ2Pau4q6c&list=PLruLh1AdY-SgW4uDtNSMLeiUmA8YXEHT_&index=12
-Chris…
as follows.
We have a grid which consists of a collection of columns, where each column consists of a list of points. You said flattening is out of the question, so we need to cull items from each list individually.
Let's say our culling pattern is KDDDKDD (repeat as needed). K = Keep, D = Ditch. If a column contains 18 points, the pattern needs to be repeated until it is 18 items long. In this case:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
K D D D K D D K D D D K D D K D D D
We can now cull each column, but they will all be culled in the same way. By shifting the pattern one more index for each column, we can cycle the culling.
The fix incidentally is to Shift the pattern PRIOR to repeating it. Then it works as expected:
--
David Rutten
david@mcneel.com
Tirol, Austria…
Added by David Rutten at 2:49pm on October 2, 2013
them into one solid).
By the reversed order of the Loft Curves, the SolidDifference is still not working when I trim the surface by a box1 which is scaled over the z axis. But it does work around the problem of the deleting curve number 13 or 11 or 5 or 4 or 0. Strange, strange strange..... Maybe something for David?
Is there an explanation why the reversed order of the lofting curves is working better?
Cheers,
Bas…
this case "13."
I am trying to find the logical way to output that item value as a percentage of the overall list's domain. For example, I need to convert 13 to a value of .5 representing it being the median value of the list. 11 would be 0.0, 12 would be .25, etc...
Any help would be greatly appreciated…
ge on top) of Sameer's definition he used:
{A;B} (i) > {A} (i)
Let's suppose that you have 5 curves selected in your definition. So you will have:
- Data with 5 Branches
- N=11 (as default value from Divide Curve)
- data structure (0;0) (0;1).....(0;4)
Here the question: WHY?? the points coming out from this Path Mapper belong to the fifth curve (and not the fourth, the third...etc.)?
Thanks a lot!…