Re: [Scilab-users] How to overload "double" function ?
Le 22/08/2018 à 18:36, Samuel Gougeon a écrit : > > So, OK, now i understand it. > IMO, the 5.5.2 code factorization was welcome. I did not go to the code > of 6.0. > Anyway, you may report the issue. done : http://bugzilla.scilab.org/show_bug.cgi?id=15722 Philippe ___ users mailing list users@lists.scilab.org http://lists.scilab.org/mailman/listinfo/users
Re: [Scilab-users] ATOMS error Scilab 5.5.2
Le 23/08/2018 à 12:53, DrVS a écrit :
Hello Samuel,
Thank you for your answer.
I've already try to install manually, but without
success.
I have this kind of message (error 1) :
/-->atomsInstall("C:\Users\vince\Downloads\coselica-0.6.6.zip")
By the way, this is a file for Scilab 6, while your problem was to
install something for Scilab 5.5.2.
So please target the right version and file!
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users
Re: [Scilab-users] ATOMS error Scilab 5.5.2
Le 23/08/2018 à 12:53, DrVS a écrit :
Hello Samuel,
Thank you for your answer.
I've already try to install manually, but without
success.
I have this kind of message (error 1) :
/-->atomsInstall("C:\Users\vince\Downloads\coselica-0.6.6.zip")
You have downloaded the sources archive instead of the binary.
The binary in named "coselica_0.6.6.zip
"
(with an undercore instead of an hyphen:
OK, this naming is really misleading)
Samuel
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users
Re: [Scilab-users] ATOMS error Scilab 5.5.2
Hello Samuel,
Thank you for your answer.
I've already try to install manually, but without
success.
I have this kind of message (error 1) :
/-->atomsInstall("C:\Users\vince\Downloads\coselica-0.6.6.zip")
!--error 1
atomsDESCRIPTIONread: The file
"C:\PROGRA~2\scilab-5.5.2\.atoms\tmp_1535021295\coselica-0.6.6\DESCRIPTION"
does not exist.
at line 46 of function atomsDESCRIPTIONread called by :
at line 160 of function atomsInstall called by :
atomsInstall("C:\Users\vince\Downloads\coselica-0.6.6.zip")/
I have also this kind of message for an other module :
/!--error 1 atomsDESCRIPTIONread: The file
"C:\Users\vince\AppData\Local\Temp\SCI_TMP_19856_\.atoms\1_TOOLBOXES" is
empty./
So, i don't know what to do...
--
Sent from:
http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users
Re: [Scilab-users] xs2svg and complex grayplot: room for improvements?
Le 22/08/2018 à 18:53, Samuel Gougeon a écrit : Hello Antoine, Le 22/08/2018 à 15:19, antoine.monmayr...@laas.fr a écrit : Hi all, xs2svg is not working well with big grayplots: the resulting svg file is too big and contains too many elements to be usable. Worse, for really big grayplots, the export fails (not enought memory). As an example, the following code: grayplot() h=gcf(); xs2svg(h,'grayplot.svg'); results in a 3.7MB svg file with 93784 elements that cannot be edited with Inkscape. The issue is that xs2svg renders each patch of the grayplot using two svg filled triangles. In "he who must not be named"¹, the svg export is using a more pragmatic approach: everything is rendered as svg path/text/whatever, except from the intensity maps (grayplots, surf, ...) that are rendered as bmp and included in the svg file. This way, the svg file is really light, can be tweaked with any svg compliant software (inkscape) and the result is really good. In practice, to get publication-quality grayplots, I tend to do the following: -hide the grayplot, keep all the rest, export to svg, -hide everything but the grayplot, export to png, -use inkscape to include the png of the grayplot and hand-place it in the svg. Do you remember Calixte's answer to you about this topic in 2012?: http://bugzilla.scilab.org/show_bug.cgi?id=11195#c1 Her, to be honest, no, I dit not remember. But Matplot() and Matplot1() are not decent solutions, just workarounds as they are way more limited than surf(), Sgrayplot(), contourf()... In particular, you cannot specify x-axis and y-axis scales using vectors, which is essential for experimental dataset that are not always regularly spaced in x- and y-. Thanks for refreshing my memory. But it means the solution exists: can't we use the same approach for other "intensity maps"? Antoine Cheers Samuel ___ users mailing list users@lists.scilab.org http://lists.scilab.org/mailman/listinfo/users -- +++ Antoine Monmayrant LAAS - CNRS 7 avenue du Colonel Roche BP 54200 31031 TOULOUSE Cedex 4 FRANCE Tel:+33 5 61 33 64 59 email : antoine.monmayr...@laas.fr permanent email : antoine.monmayr...@polytechnique.org +++ ___ users mailing list users@lists.scilab.org http://lists.scilab.org/mailman/listinfo/users
Re: [Scilab-users] {EXT} xs2svg and complex grayplot: room for improvements?
Le 23/08/2018 à 09:09, Dang Ngoc Chan, Christophe a écrit : Hello, De : antoine.monmayr...@laas.fr Envoyé : mercredi 22 août 2018 15:19 In "he who must not be named"¹, the svg export is using a more pragmatic approach: everything is rendered as svg path/text/whatever, except from the intensity maps (grayplots, surf, ...) that are rendered as bmp and included in the svg file. In addition to Samuel's answer, I wonder why using the SVG format to handle a bitmap. Well, because that's a required step in the right direction (pdf) to get publication-quality graphics that are relatively good at various scales. The idea is to keep the vectorial format for scales, lines, text and get a bitmap for what is essentially a bitmap! You get the best of both world. Antoine It seems to me that the SVG format is just not adapted to the case. -- Christophe Dang Ngoc Chan Mechanical calculation engineer This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error), please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. -- +++ Antoine Monmayrant LAAS - CNRS 7 avenue du Colonel Roche BP 54200 31031 TOULOUSE Cedex 4 FRANCE Tel:+33 5 61 33 64 59 email : antoine.monmayr...@laas.fr permanent email : antoine.monmayr...@polytechnique.org +++ ___ users mailing list users@lists.scilab.org http://lists.scilab.org/mailman/listinfo/users
Re: [Scilab-users] {EXT} xs2svg and complex grayplot: room for improvements?
Hello, > De : antoine.monmayr...@laas.fr > Envoyé : mercredi 22 août 2018 15:19 > > In "he who must not be named"¹, the svg export is using a more pragmatic > approach: > everything is rendered as svg path/text/whatever, > except from the intensity maps (grayplots, surf, ...) > that are rendered as bmp and included in the svg file. In addition to Samuel's answer, I wonder why using the SVG format to handle a bitmap. It seems to me that the SVG format is just not adapted to the case. -- Christophe Dang Ngoc Chan Mechanical calculation engineer This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error), please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. ___ users mailing list users@lists.scilab.org http://lists.scilab.org/mailman/listinfo/users
