MoI discussion forum
MoI discussion forum

Full Version: Nodebundle for playing with nodes

Show messages:  1-5  …  566-585  586-605  606-625  626-645  646-665  666-685  686-705  …  1846-1859

Thread Split: Some posts in this thread have been moved here

Message 7777.626 was deleted


From: speedy (AL2000)
19 Oct 2017   [#627]
Hi Friends,

this is the fourth Macro ;
Cubic Bezier from 4 points .
The interesting thing, I think, is that we can use it
not just isolated points, but also points that lie on curves
linear .....
in this case the output curve represents a particular fillet
between these two curves ...

input

point 1
point 2
point 3
point 4
Start Domain
End Domain
n°point for curve

output

Cubic Bezier
Points Control Polygon
Control Polygon

Files at this link;
http://www.mediafire.com/file/ddh3c95syhwxphb/M-Cubic_Bezier_from_4_Pt.rar
Have a nice day to all
alberto
From: bemfarmer
19 Oct 2017   [#628] In reply to [#627]
The download link does not work.
Even exclusion from Malwarebytes does not help.
- Brian
From: Karsten (KMRQUS)
19 Oct 2017   [#629] In reply to [#628]
Hello Brian,

here is Als the node file.

Have a nice day
Karsten

Attachments:
Dim-Macro Bezier from 4 point.nod


From: speedy (AL2000)
19 Oct 2017   [#630]
Hi Brain
if you refer to my last file
I checked in the site, and they made 2 Downloads,
maybe it's a problem with your Server.....
best
alberto
From: speedy (AL2000)
19 Oct 2017   [#631]
Thanks Karsten for putting the file in the forum ...
I still can not use Mediafire
(they are still the effects of the Earthquake in my Territory)
thanks again and have a nice evening
alberto
From: bemfarmer
19 Oct 2017   [#632] In reply to [#629]
Thank you Karsten

A new experience:
About a half hour after trying the download, doing some Math google searches, my speaker started a noxious pulse beeping, one webpage screen went red, with some warning to call an alleged "Microsoft" telephone number, some blocked malware was after bank accounts and credit cards, etc.
(No fault of MoI, nor of MediaFire as far as I know.)
Rebooted, and all seems well.

- Brian
From: Karsten (KMRQUS)
19 Oct 2017   [#633] In reply to [#632]
Hello Brian,

I saw this pop up also. Go to task manager and kill the process. I got always pop ups at mediafire, but never such crap like in the last days.

p.s.: Under linux you will get 15€ for a bet portal;-)
From: James (JFH)
21 Oct 2017   [#634]
Hi All,

UPDATE: Revised version can be found here:
http://moi3d.com/forum/index.php?webtag=MOI&msg=7777.649

I have attempted to recreate a form as per youtube vid:
https://www.youtube.com/watch?v=kiKG-vkTzfE
Not emulating the procedure, just the end result.



WARNING: Due to the sheer complexity of the form (number of lines/surfaces),
running the .nod file will take a long time to render to screen
(approx. 40 secs on my laptop), so be patient.
Of course, for denser meshes, it will be even longer.



Have a great weekend
James
From: mkdm
22 Oct 2017   [#635] In reply to [#634]
Hi James!

Thanks a lot for this sharing!

What a complex and beautiful node ! A lot of stuff useful for practicing.

On my PC i7-7700K it takes exactly 30 secs to generate the output.

Ciao!
From: Mike (MGG942)
22 Oct 2017   [#636] In reply to [#634]
Great stuff. Bit hard to tell - is this a moebius strip?

I'll have to update my machine - 44.5 seconds. Though the processor is an i7.
Perhaps a better graphics card - currently an AMD Radeon HD 7800
From: James (JFH)
22 Oct 2017   [#637] In reply to [#636]
UPDATED: mobius2.nod attached

(Further simplified; previous version still contained extraneous nodes
related to retopologizing the surface in prep for mFlow)


Hi Mike,

<< is this a moebius strip?>>

Yes, try this .nod file:
same circuitry, but without the variable fenestration.
(with next to no delay to generate output )

James
From: mkdm
22 Oct 2017   [#638] In reply to [#636]
Hi Mike!

@You : "...I'll have to update my machine - 44.5 seconds. Though the processor is an i7. Perhaps a better graphics card - currently an AMD Radeon HD 7800"

Well, I'm not Michael but for what I know about how Moi deals with calculation I think that it actually doesn't use almost anything of GPU power (unfortunately)
except display and render meshes.

So I think you will get no advantage upgrading your GPU.

Consider that I currently own a Gtx 1080 Ti.

Ok, Vega cards and also some previous generation "gaming" Amd GPUs are more powerful regarding FP64 and FP16,
but with Gtx 1080 Ti we are still talking about something like 11 TFlops in FP32 with 11Gb or superfast video memory.

Talking about the CPU not all i7 are the same.

I currently have the most powerful 4 cores/8 threads cpu currently available, the i7-7700K, but anyway it has only 4 physical cores
and I know that a CPU with more cores like Threadripper or other Intel CPUs are much more powerful than my 7700K.

So, if you are thinking about upgrading, at least talking about Moi, I think you should switch to a new CPU with more cores.

but you should ask to Michael if Moi can leverage on more cores and if the gain is "linear".
I mean, for example, 40 secs to execute that nod file with a 4 cores CPU, so...20 secs with 8 cores ?

I hope i made myself clear enough :)

Ciao!
From: Michael Gibson
22 Oct 2017   [#639] In reply to [#638]
re: multiple cores - MoI makes use of multiple CPU cores for part of the viewport graphics display and when generating meshes for export to a polygon format. Other areas like a node calculation will run on a single core. It takes special work to use multiple cores, it involves breaking things down into individual isolated task units which can then be scheduled across threads. That's very different than "normal" code.

- Michael
From: Mike (MGG942)
22 Oct 2017   [#640] In reply to [#637]
Thanks, James.
I'm a bit obsessed with Moebius strips so I shall enjoy studying this simpler nod.
Mike.
From: Mike (MGG942)
22 Oct 2017   [#641] In reply to [#638]
Thanks Marco and Michael.

My i7 is a humble 3770 @ 3.40 GHz.

Good enough for a while yet.

Mike.
From: James (JFH)
22 Oct 2017   [#642] In reply to [#640]
Hi Mike,

<<I'm a bit obsessed with Moebius strips so I shall enjoy studying this simpler nod.>>

I have uploaded simpler mobius2.nod file tp previous post:
http://moi3d.com/forum/index.php?webtag=MOI&msg=7777.637

If the profile shape is even sided & the number of twists is odd (or vice versa )
the resultant form will be single-sided solid. Which is to say it could be
unrolled into a continuous looped strip.

I encourage you to indulge your obsession,
James
From: mkdm
23 Oct 2017   [#643] In reply to [#639]
Hi Michael.

Thanks for confirming my words.

@You : "...Other areas like a node calculation will run on a single core. It takes special work to use multiple cores, it involves breaking things down into individual isolated task units which can then be scheduled across threads. That's very different than "normal" code..."

It' true, and unfortunately this is still one of the main "Achilles heel" of almost all 3D cad/nurbs modeler.
I mean, the lacks of multicore capabilities for almost all their features.

And this is really a big "hole" because actually if you really want to speed up things in one of these software, including Moi or Rhino,
maybe the one and only way to go is to buy a very expensive CPU with a high IPC and fast and big internal cache.

And actually, for what I know, only very expensive CPU like the XEON line have this characteristics.

All other CPU, including new AMD Threadripper or even all i9 from Intel, although they can run at a higher clock speed,
they cannot reach the IPC value and the overall computing power of a XEON.

So, unfortunately, today the main bottle neck is not the hardware but the SOFTWARE. Almost ALL software!

The main problem is that is really very expensive, especially for a little company or a one person company, to afford the investment that
is necessary to build and maintain the development of a multi core application.

So, actually most of the money we spend to buy new CPU with lots of cores is almost totally wasteful.

Fortunately all these consideration doesn't apply to GPU computing, but here, again, the "Achilles heel" is that only a little portion of calculation
can be demanded to GPU. Only specific types of tasks.

Maybe in the next years we will see a new generation of code compiler that will provide a much robust and wider range of multi core capabilities :)


Have a nice day Michael.

Ciao!
From: Michael Gibson
23 Oct 2017   [#644] In reply to [#643]
Hi Marco, just to clarify - as I mentioned above MoI does make use of multiple CPU cores for the viewport display and for mesh format export. The display is something that is in constant use and so I'm not sure why you'd consider that to be totally wasteful... ?

But because it's difficult to implement it makes the most sense for me to focus multi core use on a few key areas that deliver a high amount of value, such as the display. The next focus area for it will probably be for generating display meshes which will then help speed up file loading for example. It's another area that gets heavy use across many different commands and use cases and so any benefit there is of high value.

Also another thing that has been a limiting factor is doing things on multiple cores can consume more memory since some operations may need to make fairly large allocations and having multiple large allocations simultaneously "in flight" could more easily exhaust 32-bit address space. With the 64-bit version I shouldn't have to worry about that as much.

- Michael
From: mkdm
23 Oct 2017   [#645] In reply to [#644]
Hi Michael.

Thanks a lot for clarifying.

@You : "...the display is something that is in constant use and so I'm not sure why you'd consider that to be totally wasteful... ?..."

Well, I said "totally wasteful" because I have considered the actual situation of CAD software in general. Not only about Moi.
At least the CAD software that are in the "consumer" market, not the "high-end".

I explain.

Ok, it's good to know that Moi deals with displaying meshes in a "multicore" fashion. Perfect!!

But, I was referring also to ALL other kind of operations. All other CPU bound operations.

For example, running each command, running each node in NE, doing any CPU bound calculation.

I'm not referring here to the part of the code that is dedicated to display and render the meshes, but to the part of the code where the calculation are carried out.

When a "Loft" or a "Network" or a "Fillet" command for example, or anything else, takes 30 secs on a given multicore CPU,
if the 90% of the time is relative to the mathematical calculation and are CPU bound, and only 10% relates to final render of the resulting mesh,
then it means that even if you have a multicore CPU, the 90% of the time is spent on a single core and only 10% can leverage on the multi core.

This is what I wanted to say when I said "totally wasteful".

I don't think I'm wrong if I think so.

Anyway, this is totally not referred specifically to Moi, but ALL software in general, so I didn't want to be critical with regard to Moi or your developing job :)

I hope I made myself clear.

Ciao!

Marco (mkdm)

Show messages:  1-5  …  566-585  586-605  606-625  626-645  646-665  666-685  686-705  …  1846-1859