Custom Functions plugin - functions: extended Max and Min, Unit of Measurement, Order of Magnitude - Messages
I must have tried a semicolon (my separator) before because I recognise what happens after the first press:
cases(■;■;■;■)
but didn't try pressing a second time!
It works for me now! :d
Thanks again
Brian
Visit this great apllication, if it works for you.
It does not work anymore for me in the UNofficial 5346 relaese.
I concluded from multiple observations that the UNofficial
release came with a TimeStamp of so long duration so that past
the "date" it does not work anymore. In Smath 5346, this work sheet
did work properly for several days in multiple PC ON/OFF, but not
anymore to my disatisfaction. I observed that one from Davide
and many more from Martin.
Jean
Convolution RC [Cases, Davide].sm (109 KiB) downloaded 138 time(s).
I had a quick look at the "T - not defined" issue. There's a workaround for SMath 0.98.5997 by including the T variable in the h(t) definition, rather than in the plot (I think I've got the '-' signs right).
Convolution_RC update.sm (10 KiB) downloaded 132 time(s).
The formula in the plot doesn't look quite as you'd expect, but I think the answer's right.
Cheers
Brian
In latest nightly build instead:
- I need the Brian's workaround to make it working the first plot (might be something in the 2D plot itself, since T is defined on the canvas);
- f(t) doesn't work anymore... I guess it might be something related to the "isUndefinedArgumetnSupported" af latest APIs, but seems there isn't a way to enable it for functions with an undefined number of arguments....

About Levemberg-Marquardt, you have to install NonlinearSolvers plugin manully form the extensions manager: http://screencast-o-matic.com/watch/cD1X6giD2p
Unfortunately doesn't fix the issue...


- cases() inner logic refactored (now acts in the same way both for numerical and symbolical evaluation);
I am trying to use the at(2) to try to evaluate a formula with several variables in one step.
OK this makes quite no sense ...but is in an attempt much more difficult to use a same symbolical equation obtained through a solve in different parts of a documents with different values of the variables without using each time the technique of the disable evaluation ( at least is the only way I have found to address this issue ... it doesn't exist a command that allow to reuse a symbolical equation after some assignment have been done to the values of the variables referenced in it ).
However in doing this I have seen a strange behaviour of the at(2) as herewith reported:
See my comments in the screenshot.
Best regards
Franco

Wrotebut is in an attempt much more difficult to use a same symbolical equation obtained through a solve in different parts of a documents with different values of the variables without using each time the technique of the disable evaluation ( at least is the only way I have found to address this issue ... it doesn't exist a command that allow to reuse a symbolical equation after some assignment have been done to the values of the variables referenced in it ).
Once the variables are unknown at the definition of eta, you can reuse it any times you need, just define again the variables' values (search it in the Dynamic Assistant, you see that no numeric values are stored); use Clear(...) if you need to show again the unknown names.
WroteHowever in doing this I have seen a strange behaviour of the at(2) as herewith reported:
This is because in the second argument of at() you are using variables already defined, therefore at() reads "7700*'kg/{'m^3}≡7700*'kg/{'m^3}" instead of "ρ_sfera≡7700*'kg/{'m^3}" -> currently you have to use Clear(ρ_sfera); I plan to improve at() with progressive preprocessing, to reduce these kind of problems (and the error message too).
I was worried that after using the 1st time an expression it was no more "live" for further usage with different values.
This till the explanation of Davide I was using the trick of the "Disable evaluation" ..but this is not very elegant and useful.
( to tell the truth I have used the clear ..but probably positioning it in an incorrect way because the result was not like the one shown by Davide )
Best regards
Franco
by itself and in Maple companionship, quite convenient for
teaching/publishing/engineering.
Visit some "solving" applications attached. Report what does
work or not clear.
Jean
Solve Maple Implict Expr.sm (48 KiB) downloaded 129 time(s).
- Abs() now is hidden from dynamic assistance and Functions dialog; consider this function deprecated and use vectorize(abs(...)) or a classic loop instead.
WroteI was worried that after using the 1st time an expression it was no more "live" for further usage with different values.
Not very clear as well as the remaining of your comment.
Smath functions are infinitely usable, including the solvers. Taking into account
what comes with the new demand and taking into account of that you are not repluging
something in a bloc that has turned red first. Generally a failed solve bloc can't be
repaired, depending upon the kind of failure.
Smath as well as Mathematica, Mathcad suffers "shadow in the context" page 7.
A bit of MicMac in long work sheets collectors type.
Jean
SolveGEN.sm (102 KiB) downloaded 111 time(s).
- Clear(...) removed (built-in and more powerful since SMath Studio 0.98.6325);
The big question is if new version will allow
updating 6179 via downloading 'patches' ?
Jean
WroteThe big question is if new version will allow
updating 6179 via downloading 'patches' ?
It is up to Andrey's choice. In theory built-in Clear(...) is coded inside SpecialFunctions.dll, so this plugin in particular could be compiled and shared thorough the extension manager for older versions, providing the core of the target version is still compatible. In practice this might introduce some problems at several levels; due to the progress in the core some built-in plugins might be more back-compatible than others or not at all (therefore some plugin might be able to go back up to version 0.97.xxxx and other to some more reccent 0.98.yyyy). This will raise other problems, such as solving bugs for multiple core+plugins combinations (community side it makes harder to help to identify and solve problems, dev side this drains time to develop and fix bugs for further versions)

- added rgb2image(...) rgb2image.sm (14 KiB) downloaded 102 time(s).;
- image2rgb(...) speed improvements;
- refactoring;
-
New Posts
-
No New Posts