If you consider laptops as something to be changed every 3 years like me: go for the Asus N550J series. i7 @2.4Ghz + 16Go RAM + nice screen + 7200RPM disk. 15 or 17", and a nice design. 1000-1300€.
ndom S (Seed)' input is different for each component in the Lynda tutorial code (8, 17, 13) but all the same (2) in your copy.
There are many ways to make the seed values different, individually or all three at once:
…
e
7. True
8. True <-- this one
9. True
10. False
11. True
12. False
13. True
14. True <-- this one
15. True
16. False
17. True
18. False
19. True
20. True <-- this one
21. True
22. False
23. True
24. False
25. True
26. True <-- this one
27. True
28. False
29. True
30. False
31. True
32. True <-- this one
33. True
Any idea how I can solve this?
Thanks!…
In this meeting we went through the second portion of Woo Jae's exercise and began exploring ways we could apply it to surfaces instead of just two lines. We are starting from the beginning.
I extract the first two with a "Redim Preserve t(1)" command.
In the first case, the redim is correct, Line 7 = Line 2 and Line 8 = Line 3. It just kept the first two values like it is supposed to be.
But, for the second curve starting Line 9, some t values are messed up after the Redim. Line 16 = Line 17 despite Line 11 was different from Line 12. That's what is creating a problem later in the Split.
Weird.
…
1D when it comes to a location on a surface or a curve. If a 3D point shares a location on a surface we can represent it by means of the U and V co-ordinates of that surface.
In your example above the 4 surface corners are {2,2.5,0}, {17, 2.5, 0}, {17, 19, 0} and {2,19,0}. Unless you reparametrise the domains they will typically take the same domains as the curves that constructed them in this particular case the lengths (but these curves are only that length at the edges and only when you created the surface).
So the U domain is 0 to 15 (17-2) and the V domain is 0 to 16.5 (19-2.5). Even if you transformed the surface to another location or another shape these domains will not change and therefore the UV co-ordinate will not change. If you reparemterise the surface then the domains are set to 0 and 1 in both directions and this might be easier to work with. You can think of them as a percentage then, a UV location of {0.5, 0.5} of a reparameterised surface will always be in the middle of the 2D space.
All points on a surface in 2D have a 3D space co-ordinate as well, but not all 3D points have a 2D co-ordinate. This is why we need to use the Surface CP to get a UV value to evaluate a surface at a given point.
Incidently the 1D co-ordinate of a curve is represented by the parameter t
…
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.
…
0,
I want to move everything in {2} up 5 and 10 and 15,
Any ideas. I have been trying using the series component to create the right data structure but somehow its not working and i am sure there is a simple way?
Do i have to repeat the data so that the number of transform data matches the input list or is there a way to simply apply the transformation to everything in {0}{1} and {2} respectively depending on its structure ??
Hopefully this makes sense? I am not really sure but is it a job for stream - i cant understand why i cant get it to work. Sorry i am sure this is covered in the forums, i have been looking but cant anything which helps specifically.
Many thanks
Chris…