DSP Robotics Support

Great job! My toolbox sends it's appreciation
I must ask something: ain't these modules a little expansive to use in term of performance? I mean, each math module contains all the math PRIM's inside while we actually use only one of them per module.

kortezzzz wrote:I must ask something: ain't these modules a little expansive to use in term of performance? I mean, each math module contains all the math PRIM's inside while we actually use only one of them per module.

That's what I'd like to know.

deleted

tiffy wrote:

kortezzzz wrote:Great job! My toolbox sends it's appreciation
I must ask something: ain't these modules a little expansive to use in term of performance? I mean, each math module contains all the math PRIM's inside while we actually use only one of them per module.

Not necessarily, it depends on the application in which it is used.

Thank you PHI, this is very handy.

why does it depend on the app?

there are lot of primitives for a operation which would need just one primitive normally, its not just the operators which are not in use, its also the knobs and the editboxes which are much worse because they include droplists, rubymodules, a lot of draw and view stuff and are up to 8 levels deep!
property controls, if you really want them to use in your final release, should always be purgeabled to not get compiled, and incresing the size, which is the biggest issue here, for prototyping to find out the best finetuning for your algo it could be pretty helpful but i wouldn't leave them inside.

just do the test and save a project with 64 ez math modules (set for adding), this needs 29KB
while when using just the add prim its 1KB

.... should always be purgeabled to not get compiled,

I've wondered the same thing

Can the entire EZMath module be made purgeabled, and keep only the required function when compiled?

deleted

Nubeat7 wrote:property controls, if you really want them to use in your final release, should always be purgeabled to not get compiled

I have no idea how to do this. I even took the time to search through the manual and component reference (the word "purge" is not even used once).

just do the test and save a project with 64 ez math modules (set for adding), this needs 29KB
while when using just the add prim its 1KB

I hope you're suggesting there's more of an impact than that. I have a hard time being concerned over 28KB. You brought up the number of modules, and it's been said that each module used has some impact on CPU, though I don't know if that's measurable. I don't think it's ever been suggested precisely how much CPU is used on modulizing.

Anyways, I specifically asked for feedback regarding performance so I appreciate the discussion.

I have no idea how to do this. I even took the time to search through the manual and component reference (the word "purge" is not even used once).

If you right-click on the module, a set of options list opens ... should be 2nd from the bottom.

NOTE: Hopefully the comments made are NOT taken the wrong way !!! I think we are looking to be 1. made aware of possible side effects, and 2. Can a module be 'improved' on any front.

The convenience of these EZMaths might not be for everyone, but they are very handy modules for sure, and appreciated that they have been made available to us. THANKS!

But IF they [or any] module can be optimized or improved, this is good learning for the FS community.

my 1/2 cent

RJHollins wrote:If you right-click on the module, a set of options list opens ... should be 2nd from the bottom.

I see, thank you. Although again, without literature on this, I can only make assumptions about what this does and how it works.

The discussion is good!

can only make assumptions about what this does and how it works.

I'm sure somebody here knows the details

My 'understating' [or lack thereof, is from looking inside different modules and seeing the dotted outline indicator that shows a purgeable state. IOW, only during EXPORT, these marked pieces are excluded from the outputted file.

There is a user built COLOUR PRIM that shows these internal signs, and maybe can serve as example.

What I don't know [in this case], if a specific function [PRIM] is marked purgeable YET, the data it provides is needed. What happens ??? I don't know Does the project break or malfunction

For so many of my little projects, the 'waste' is so minimal to worry .... but when we see some of the monster projects that users have built, the potential could be significant.

It would be good to learn more about this, maybe someone can shine a light