ay how many valid permutations exist.
But allow me to guesstimate a number for 20 components (no more, no less). Here are my starting assumptions:
Let's say the average input and output parameter count of any component is 2. So we have 20 components, each with 2 inputs and 2 outputs.
There are roughly 35 types of parameter, so the odds of connecting two parameters at random that have the same type are roughly 3%. However there are many conversions defined and often you want a parameter of type A to seed a parameter of type B. So let's say that 10% of random connections are in fact valid. (This assumption ignores the obvious fact that certain parameters (number, point, vector) are far more common than others, so the odds of connecting identical types are actually much higher than 3%)
Now even when data can be shared between two parameters, that doesn't mean that hooking them up will result in a valid operation (let's ignore for the time being that the far majority of combinations that are valid are also bullshit). So let's say that even when we manage to pick two parameters that can communicate, the odds of us ending up with a valid component combo are still only 1 in 2.
We will limit ourselves to only single connections between parameters. At no point will a single parameter seed more than one recipient and at no point will any parameter have more than one source. We do allow for parameters which do not share or receive data.
So let's start by creating the total number of permutations that are possible simply by positioning all 20 components from left to right. This is important because we're not allowed to make wires go from right to left. The left most component can be any one of 20. So we have 20 possible permutations for the first one. Then for each of those we have 19 options to fill the second-left-most slot. 20×19×18×17×...×3×2×1 = 20! ~2.5×1018.
We can now start drawing wires from the output of component #1 to the inputs of any of the other components. We can choose to share no outputs, output #1, output #2 or both with any of the downstream components (19 of them, with two inputs each). That's 2×(19×2) + (19×2)×(19×2-1) ~ 1500 possible connections we can make for the outputs of the first component. The second component is very similar, but it only has 18 possible targets and some of the inputs will already have been used. So now we have 2×(18×2-1) + (18×2-1)×(18×2-1) ~1300. If we very roughly (not to mention very incorrectly, but I'm too tired to do the math properly) extrapolate to the other 18 components where the number of possible connections decreases in a similar fashion thoughout, we end up with a total number of 1500×1300×1140×1007×891×789×697×...×83×51×24×1 which is roughly 6.5×1050. However note that only 10% of these wires connect compatible parameters and only 50% of those will connect compatible components. So the number of valid connections we can make is roughly 3×1049.
All we have to do now is multiply the total number of valid connection per permutation with the total number of possible permutations; 20! × 3×1049 which comes to 7×1067 or 72 unvigintillion as Wolfram|Alpha tells me.
Impressive as these numbers sound, remember that by far the most of these permutations result in utter nonsense. Nonsense that produces a result, but not a meaningful one.
EDIT: This computation is way off, see this response for an improved estimate.
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
Added by David Rutten at 12:06pm on March 15, 2013
Both a date and a time (11:35 on September 4th, 2010)
The .NET DateTime structure only really supports the third. It counts the number of 'ticks' (1 tick = 100 nanoseconds) since midnight on January the first in the year 1. It does not support any moment in history before the year 1, it does not support any date beyond the year 9999 (ok, not a big drawback that one) it does not support calendars other than Gregorian, it does not support time zones, it does not allow you to just specify a time only and leave the date blank or vice versa.
Some of these shortcomings can be hacked onto the structure, basically by hijacking the tick count and assigning special meaning to certain small tick offsets, but there's always trade-offs with such an approach.…
Added by David Rutten at 6:55am on January 27, 2016
owing error has been raised: System.Runtime.InteropServices.COMException (0x80040154): Retrieving the COM class factory for component with CLSID {CE7E6869-6F74-4E9D-9F07-3DCBADAB6299} failed due to the following error: 80040154 没有注册类 (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)). at System.Runtime.Remoting.RemotingServices.AllocateUninitializedObject(RuntimeType objectType) at System.Runtime.Remoting.Activation.ActivationServices.CreateInstance(RuntimeType serverType) at System.Runtime.Remoting.Activation.ActivationServices.IsCurrentContextOK(RuntimeType serverType, Object[] props, Boolean bNewObj) at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at Microsoft.Scripting.Interpreter.NewInstruction.Run(InterpretedFrame frame) at Microsoft.Scripting.Interpreter.Interpreter.Run(InterpretedFrame frame) at Microsoft.Scripting.Interpreter.LightLambda.Run3[T0,T1,T2,TRet](T0 arg0, T1 arg1, T2 arg2) at System.Dynamic.UpdateDelegates.UpdateAndExecute2[T0,T1,TRet](CallSite site, T0 arg0, T1 arg1) at Microsoft.Scripting.Interpreter.DynamicInstruction`3.Run(InterpretedFrame frame) at Microsoft.Scripting.Interpreter.Interpreter.Run(InterpretedFrame frame) If upper error is:1) "Retrieving the COM class factory for component with CLSID…" then try the following fix: a) Close Rhino. Restart your PC. Once the PC boots up, double click on the "regMapWinGIS.cmd" file in "MapWinGIS" installation folder. When it closes the Command Prompt window it opened, try running Rhino, Grasshopper and the component again. b) If the upper COM class error appears again, then close Rhino, and uninstall the MapWinGIS application. It is advisable to do that with an application which does that by removing not only the installation files but also the leftover files (like those from registry). For example, use the: Revo Uninstaller Pro. A free 30 days full working version can be downloaded from: http://www.revouninstaller.com. After the Revo Uninstaller Pro uninstalls MapWinGIS, install it again, but this time by running the installation file by right clicking on it, and choosing: Run as -> Administrator. After the installation is complete double click on "regMapWinGIS.cmd" file in "MapWinGIS" installation folder. When it closes the Command Prompt window it opened, try running Rhino, Grasshopper and the component again. If after this the COM class error appears again, then post a question about this issue at: http://www.grasshopper3d.com/group/gismo/forum. 2) If the upper error is not "Retrieving the COM class factory for component with CLSID…", please post a question about this issue at:http://www.grasshopper3d.com/group/gismo/forum.…
Added by Elise to Gismo at 6:11am on November 13, 2019
ious tasks and am very pleased to do so. I was guessing but couldn't properly explain that there are impossible solutions due to a given setup.
Still, was almost hoping that you would step in on this discussion :) the sphere packing looks great, was trying with spheres last night, but didn't get anywhere yet. Actually would you mind sharing the definition? Looks like it actually could solve the issue! Do you think it would even work with very large numbers of knots? Like 10000+? The stepping, is it imaginable with any value like i.e. 15 20, 35, 39, 60,...?
Thanks very much,
Oliver
…
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.…
bounding box wont work because it will seldom be square shaped. this square bounding surface should always be larger than the open or closed curve
2. dividing the curve into then testing its closest point to the center of the bounding sqaure plane.
3. creating rectangles with the same size as the divisions of the bounding plane.
this works perfectly, but there is one last problem that needs attention.
it generates the same amount of closest points than what is specified for the curve divide. e.g. the curve can be closed for instance with 35 squares , but the curve was divided into let say 50 points. the curve will be closed with the 35 squares but there are an additional 15 squares ontop of the 35 squares.
SO if someone can tell us how to remove duplicate data from a list of points(the points with the same coordinates), then the final solution will have no duplicate data.
the duplicate data can be seen in the second image
Gordon
…
e this it's really cheap if we can make a 3+ group.
The prize is 35€ per hour no matter how many students, so if there are 5 students, prize for each will be 7€ per hour (quite good)
I want to do this course, but only if atleast 2+ people join, so it's cheaper...
And i'd like to do it the last days of august/23 fisrt days september, Its a 50h course, in 3 weeks its done (4h a day)
Please, if you are interested, contact me by sending me a PM or an email@ archimint00@gmail.com
Please if you know someone that could be interested in doing it, iltll help!
Thanks!…