sität der Kreativwirtschaft) den heurigen "3D Austria Tag" ankündigen zu dürfen:Vortragsprogramm:Einlass ab 9:009:30 – 10:30: Virtuelle Landschaften mit VUE xStream Vortragender: Helge Maus (pixeltrain)10:45 – 11:30: Interaktive Anwendungen mit Unity Pro Vortragender: Dietmar Godina (Playpublic)11:45 – 12:30: Praxisbeispiele & Neuheiten zu Rhino 5 Vortragende: Albert Wiltsche und Markus Manahl (TU Graz)12:30 – 13:15: Mittagspause13:15 - 14:00: Praxisvortrag: Architectural Rendering mit VRay, 3DStudio max und Photoshop Vortragender: Martin Frühwirth (Atelier Frühwirth)14:15 – 15:00: Praxisbeispiel: Mercedes A-Klasse Präsentation mit Cinema 4D & V-RAY Vortragender: Niki Vuckovic (immortal-arts)15:15 - 16:00: Praxistipps & Neuheiten zur Adobe CS6 Vortragender: Martin Dörsch (Adobe)16:15 – 16:30: Adobe Team Cloud & VIP Lizenzprogramm Vortragender: Markus Fiala (CG Shop)16:45 – 17:45: VFX-Workflow für Guerillas - Hollywood mit SynthEyes, Cinema 4D, und AfterEffects & Plugins Vortragender: Helge Maus18:00 Ende der VeranstaltungIm Foyer werden wir Infostände von Autodesk, Chaosgroup (V-RAY) und Rhino haben - nützen Sie die Gelegenheit und informieren Sie sich - neben den Vorträgen - auch persönlich an den Infoständen bei unseren Experten!Die Teilnahme ist KOSTENLOS, aufgrund der begrenzten Platzanzahl ist jedoch eine Anmeldung per e-mail an office@kkkc.at erforderlich.…
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.
…
I have this :
list 3 : 0 1 2 3 4 5 6
list 2 : 0 1 2 3 4 5 6
list 1 : 0 1 2 3 4 5 6
list 0 : 0 1 2 3 4 5 6
and I want to group the points of index 0 in a branch, the points of index 1 in another branch and so on.
I attached a file in which I generated the points.
Thank you in advance for your help !
Regards
Red…
cture, Rhino treats them as a single flat list. For example a surface can have 10 rows and 6 columns of control-points, resulting in a list of 60 points.
But 10 times 6 isn't the only way to get to 60. If you want to make a surface out of a list of 60 points, you'll also have to tell Rhino how those 60 points should be interpreted in terms of a grid. It could be 2*30, 3*20, 4*15, 5*12, 6*10, and all of the aforementioned products the other way around.
Sometimes there's only one way for a number of points to fit into a rectangular grid. For example if you provide 49 points, then 7*7 is the only way to make it work, but these cases are rare so we always demand you give us all the information required to actually make a rectangular grid of control-points from a linear collection.
As for "Why is it, sometimes we need to attach additional value into it?", this is usually because when you divide a domain or a curve into N segments, you end up with N+1 points. For example take the domain {0 to 5}, and divide it into 5 equal subdomains. You end up with {0 to 1}, {1 to 2}, {2 to 3}, {3 to 4} and {4 to 5}. However there are six numbers that mark the transitions between these domains 0, 1, 2, 3, 4 and 5. This is why you often have to add 1 to the UCount, because the number that controls the UCount often results in N+1 actual points.…
Added by David Rutten at 8:30am on December 25, 2014