on that same PC or maybe even Dynamo. Or manual installation of 2.7.5 version. Once you installed either of these they somehow "interfered" with IronPython 2.7.0.
For some reason the strptime function you posted in your first post fails to work on IronPython 2.7.5. I do not know why is that so, I need to ask IronPython support.Still in case I get the answer: Gismo is at the moment targeted towards Rhino 5, and I won't be making it work on Rhino WIP until Rhino 6 is released. So it may be that I can not solve your issue, unless you either use a different PC, or uninstall Rhino WIP and Dynamo (I understand that this is highly unlikely).I deeply apologize for this kind of inconvenience.…
Added by djordje to Gismo at 9:57am on February 7, 2017
pen Brep"; I didn't know it worked on flat surfaces. And I think it's only fair to include in your benchmark the considerable time 'SUnion' takes in this example: 21.9 seconds for 121 rings and likely much more with 400 or 1,000+ rings.
Then I noticed the pattern doesn't match. Checked the circles and they are the same. The distance between them, however, is different: 7 instead of 6. When I change that value to 6, the Python fails badly. All the holes and gaps are gone, which destroys the pattern:
I can't do the "two phase" approach on an 11 X 11 grid, but I can do 6 X 6 and 2 X 2 to get a 12 X 12 grid (40 'SUnion' operations) in 28 seconds total. That beats your benchmark of ~37 seconds for an 11 X 11 grid, if you include the 'SUnion' in your code.
…
triangulate my mesh faces thus i was getting 7 points per polygon. 7 outputs needed. It works with 7 outputs even if 3 of them are not being used.
Problem solved!
Thanks so much for your help!
…
find a solution. At least it looks that way on my PC.
I lowered the number of decimal places to 1 (to save the time), and this is the closest result:
http://www.dodaj.rs/f/3Y/Ih/4QqtFuQy/proba.jpg
…
than v4.9.6.1.
Do you have administrators rights on your PC? Or is that office PC?
1) Download Revo: https://www.revouninstaller.com/start-freeware-download, install it.2) Uninstall MapWinGIS with it.3) Download MapWinGIS from here: https://github.com/MapWindow/MapWinGIS/releases/download/v4.9.6.0/MapWinGIS-only-v4.9.6.1-x64.exe4) Once the MapWinGIS file is downloaded, right-click on it, and choose: 'Run as Administrator'. Complete the installation.Does that make any difference?…
Added by djordje to Gismo at 1:07pm on January 19, 2021
and a "coral growth" simulation (f=.0545, k=.062)." the scale of the pattern is dependent upon resolution (200 ?) and diffusion B (0.4 ?).
For the scale in z, you have to test in 2d first and see when the pattern is what you want. So you have a number of steps, say 1200 steps and if you want 200 slices in z you need to put "steps between images" to 6 (1200/200).…
he canvas redrawing and the Rhino viewport redrawing take some time as well (on my system 6 ms for the empty Gh canvas and 28 ms for the empty Rhino viewport). No timer can avoid that, to my knowledge. The trampoline computes timing after the solution is complete. This means that one cycle is: solution completed + drawn + user specified interval.
Hope that this helps to get started,
- Giulio________________giulio@mcneel.com…
add another "trivial" constrain to the puzzle (for instance the PC sheets are 1.2*2.2m > meaning the obvious). This is addressable ONLY via the black bill (don't even think to use GH components for solving similar stuff).
3. One-off nodes are probably OK BUT for larger scales you'll need MERO type of approach > meaning assembly/component concepts > meaning dealing with instance Rhino definitions: blocks in plain English (don't even think to use GH components for solving similar stuff).
4. "Engulfing" type of strut extrusions are rather the best option (use aluminum in this case) > meaning profiles that can "wrap" the triangle content edge (be that "paper" or Lexan/PC).
5. The whole thing appears "easy" but on a pro level is rather quite challenging and obviously totally undo able without the black pill.
6. So: mesh relaxation <> adapter topology matters <> pack issues <> component design <> triangle content design <> cost <> you named it (for <> read "interact").
Such a "simple" case ... eh? …