[Plugin] Tube cutting optimisation

glro

Hello !

Just post new version that solve some of your issue. Main improvement is in vector auto-detection.
It try to find which dimension was change between component original definition and the component instance you selected. If within change (you didn't scaled selected component), the plugin try to find the biggest dimension axis in the component. If it's a cube (grrr...) then the plugin doesn't not define a vector, so user must define it. In any case user can change the vector afterward.

I take into consideration, for next update, your requests :

add cutting width parameter (should not be so complicated)

Try to develop model structure to look component included in sub-components.

I'll try to implement a option to list only components in selected entities of the model (to avoid listing all "tubes" of the model).

See you after some hours of coding ;o)

Inteloide

thank you, you repaired everything

JClements

I could not get the latest version to accurately work at all.
Try the attached file.

test 2 for counting component.skp

glro

@jclements said:

I could not get the latest version to accurately work at all.
Try the attached file.

[attachment=0:q94of7rb]test 2 for counting component.skp[/attachment:q94of7rb]

downloaded the file
plugin didn't work
switched units to millimeters
the plugin worked...

concersion issues...?

inteloide

Just post version 1.2.1 which correct your bug (html bug actually).

Inteloide

inteloide

Big correction just post.
Also cut width function added

Now I'll work on multi-tube lengthes cutting optimization as per JClements request.

Version 1.3.0 Improvements :
ADDED :		Cut width taken into account
		CORRECTED :	Errors with inches unit in optimisation. Now user can enter " or ' in tubes' length or loss or cut
		CORRECTED :	Scan also groups and other components entities
		CORRECTED :	Javascript errors make a bugsplat screen appear
		CORRECTED :	Avoid bug with components names

inteloide

Hello,

Last version (1.4.0) includes some corrections and optimization.

Mainly (for JClement) it allows to calculate cutting from different uncut tube sizes. Just enter tube sizes with a '/' between each.

In next revision, I'll include a crash preventer function, because, if you enter wrong parameters in tube cutting optimization (for example without a loss allowable and a big number of tubes), you may have some cases where calculation will take hours... For example a model with 30 tubes may have 10^32 solutions to be computed...

Inteloide

JClements

I couldn't get the "slashes" ( / ) to work for multiple source lengths.

inteloide

Hello everybody !

Can somebody try the new version to check if everything goes ok ?
Then I'll post it in pluginstore.
Thank you.

NB : I added an help file to explain how to use it.
Inteloide

glro

@inteloide said:

Hello everybody !

Can somebody try the new version to check if everything goes ok ?
Then I'll post it in pluginstore.
Thank you.

NB : I added an help file to explain how to use it.
Inteloide

it seems to be working fine

i don't understand the concept of "waste allowed", though
since the goal is to minimize the waste (loss...)it should be put at 0 everytime, no?
what is the use of a limit?
i tried to change it and the result is the same

inteloide

Waste allowed is for the plugin algorithm : if, during calculation, it found a solution with a loss shorter than "allowable waste" then plugin will not to find better solution : it's faster...in some case

inteloide

Hello,

Just post new version :
ADDED : Translation in French. Other translation can be proposed by used in translating file BGSketchup/Tube_cutting_optimisation/Rb/Localization.rb
ADDED : Link to help file in status bar
ADDED : Help file directly into the plugin rbz file
CORRECTED : "Check for update option" didn't work, now solve
OPTIMIZED : Optimized scripts for statistics

Best regards
Inteloide (BGSketchup)

inteloide

Hello,

New version added. Download, can be done directly from pluginstore now.
Some corrections inside :

1.6.1	CORRECTED :	Prevent error when calculation is on selected entities
		CORRECTED :	Design issue on update splash screen
		CORRECTED :	Little issue in stats system