Le 10/05/2021 à 15:35, Clément David a écrit :
-Original Message-
From: users On Behalf Of Antoine
Monmayrant
Sent: Monday, May 10, 2021 1:02 PM
To: users@lists.scilab.org
Subject: Re: [Scilab-users] Scilab compilation from scratch (was Re: spec can
crash scilab)
Le 10/05/2021 à 09
Le 10/05/2021 à 10:25, Stéphane Mottelet a écrit :
I added also 'F77=gfortran-8' in the configure.
What do you mean?
As a command line option to configure?
Antoine
___
users mailing list
users@lists.scilab.org
Le 10/05/2021 à 09:12, Clément David a écrit :
To fix, remove libstdc++.so and libgfortran.so on the Prerequirements;
Er, OK, I'm glad to do that, but I don't see what you are talking about.
Where are those 'Prerequirements' defined?
(I'm really not versed into compiling, I just barely know
Hello all,
Here is another update: success!
After a lot of LD_PATH, ln & -lrandomstuff dark magic that I don't
really understand I managed to compile scilab under linux ubuntu 18.04.
Se below what I've done for those interested.
A bit of warning: I tried to remove all the intermediate failures
ight comes from a wrong jdk version, you should have
openjdk8 installed on your machine and it should be listed at
configure time. Could you post the config.log file for further
investigation ?
Thanks,
Clément
-Original Message-
From: users On Behalf Of Antoine
Monmayrant
Sent: Fr
Hello all,
In order to try to mitigate bug 15330, I try to compile scilab from
source on Linux Ubuntu 18.04 64bits.
I follow the explanations from
https://wiki.scilab.org/Compilation%20of%20Scilab [Linux x86_64 cheat
sheet].
Sadly, I don't go really far as the prebuild of java fails:
Hello,
On 07/05/2021 08:57, Federico Miyara wrote:
Dear all,
If I run this simple code
ascii([ascii("hello"), 13,10, ascii("world")])
Scilab crashes. I should get something like this:
"hello
world"
Is it a bug?
Well, when Scilab crashes, it's always a bug! :-)
On my system it does not
Hello all,
Well, my workaround works up to a certain point.
When I increase the size of the matrix under study, I face another
blocking issue:
free(): corrupted unsorted chunks
Antoine
On 05/05/2021 09:23, Antoine Monmayrant wrote:
Hello all,
I might have found a workaround, but I still
it.
Could my workaround help investigate where the bug is in the gateway
between scilab and lapack?
Cheers,
Antoine
On 05/05/2021 08:22, Antoine Monmayrant wrote:
On 05/05/2021 00:09, Samuel Gougeon wrote:
Le 04/05/2021 à 16:38, Antoine Monmayrant a écrit :
Yes, it does the same
So
On 05/05/2021 00:09, Samuel Gougeon wrote:
Le 04/05/2021 à 16:38, Antoine Monmayrant a écrit :
Yes, it does the same
So this bug is still a problem, at least on Ubuntu.
Can you guys try to run spec.tst on his machine and comment on
https://bugzilla.scilab.org/show_bug.cgi?id=15330
://bugzilla.scilab.org/show_bug.cgi?id=15330
S.
Le 04/05/2021 à 16:27, Antoine Monmayrant a écrit :
Hello all,
I've been fighting during the last few days to nail down a
segmentation fault in scilab, that seems to plague linux but not
windows.
Could you try to reproduce it?
Just save the two
Hello all,
I've been fighting during the last few days to nail down a segmentation
fault in scilab, that seems to plague linux but not windows.
Could you try to reproduce it?
Just save the two attached file in a folder, cd to it and run the script.
On my machine¹, the call to spec with one
Hello Anna,
3 points:
(1) Could you post a minimum working example?
Because your code below cannot run, many variables are missing.
(2) Usually, you'd better use xload/xsave to save & restore graphics
(3) There seems to be a bug, as the following code:
h=scf()
plot()
On 14/04/2021 14:21, arctica1963 wrote:
Sorry, I did not make it clear.
Instead of the following which updates the existing graphic to generate the
final plot (y1 to y10);
plot(-[t(n) t], [0 y1])
plot(-[t(n) t], [0 y2])
plot(-[t(n) t], [0 y3])
plot(-[t(n) t], [0 y4])
plot(-[t(n) t], [0 y5])
Hello Lester,
On 14/04/2021 12:17, arctica1963 wrote:
Is there a way to do a loop over the curves to save multiple plots
What do you want to do exactly?
Do you want to get several image files with only part of the lines or
surfaces visible?
Because you can do that by playing with the
Hello Nicolas,
J'ai une un retour en direct de la troposphère du CNRS:
- Oui, il y a la volonté d'ouverture à des postes DR extérieurs.
- Il faut candidater dans une section, typiquement une section qui
correspond bien au labo que tu vises.
- Si tu es classé sur la liste principale lors du
On 10/04/2021 23:58, Heinz Nabielek wrote:
On 10.04.2021, at 08:10, Antoine Monmayrant wrote:
On 09/04/2021 23:55, Heinz Nabielek wrote:
xfpoly does generally a good job for me, sometimes I would wish that the
filling colour could be made transparent.
This is a much needed improvement
On 09/04/2021 23:55, Heinz Nabielek wrote:
xfpoly does generally a good job for me, sometimes I would wish that
the filling colour could be made transparent.
This is a much needed improvement of the scilab graphical stack that
currently does not provide any transparency.
I think this is not
On 09/04/2021 17:57, Samuel Gougeon wrote:
Dear all,
I am wondering about precedence rules when a user's defined builtin
(possibly from an ATOMS external module) has the same name than a
native Scilab builtin function.
The case appeared (and maybe still) when using the scicv external
Hello all,
I think I answered this question before on this mailing list...
Ah, yes I did:
http://mailinglists.scilab.org/Reg-Area-Between-two-curves-td3393261.html#a4026721
Get the source for "[h,epoly,ey1,ey2]=BetweenCurves(x,y1,y2,varargin)"
in the thread.
Hope it helps,
Antoine
On
On 02/04/2021 12:16, CRETE Denis wrote:
Hello,
I am also in favour of including this function in Scilab, with an
“improved” name. However, as far as I know, an inset has very
frequently its own pair of axes, as opposed to a ticks-switching in
(only one of) the axes. Thus, I would not
Le 12/03/2021 à 15:06, Jean-Yves Baudais a écrit :
OK, and you see this issue on both?
The fisrt time on 18.04 (laptop) and the second on 16.04 (desktop PC).
Are you using a wayland session or an Xorg one?
XDG_SESSION_TYPE=x11 on both
OK, I let your test running for a long time on a 18.04
On 12/03/2021 15:06, Jean-Yves Baudais wrote:
OK, and you see this issue on both?
The fisrt time on 18.04 (laptop) and the second on 16.04 (desktop PC).
Are you using a wayland session or an Xorg one?
XDG_SESSION_TYPE=x11 on both
OK, I'll have to check, I think I can get my hands on a
Hello Jean-Yves,
I also ran your test under linux (Ubuntu 18.04, Xorg) and did have any
problem (I went beyond i=10^8).
What is your specific distro and window manager?
Antoine
Le 12/03/2021 à 11:09, Jean-Yves Baudais a écrit :
Hello Stephan,
To be honest, I don't know where my problem
On 11/03/2021 11:08, Jean-Yves Baudais wrote:
Hi Antoine,
Are you running scilab under Linux?
Yes.
It might not be related, but I noticed that when my computer resumes
from sleep, all the scilab GUI is unresponsive.
I removed all sleep modes on my computer (to maintain VPN access and get
Hello Jean-Yves,
Are you running scilab under Linux?
It might not be related, but I noticed that when my computer resumes
from sleep, all the scilab GUI is unresponsive.
I don't have this issue when running scilab-cli.
Can you run your long simulation without gui?
Antoine
Le 10/03/2021 à
Hello Jean-Yves,
There is a memory leak, in interp, not splin.
Could you create a bug report?
Antoine
///
test=%t; // no leak if true, leak if false
niter=100;
mems=zeros(1:niter+1)*%nan;
is=0:niter;
h=scf();
mem=evstr(tokens(unix_g('free -b| grep ''Mem:'''))(3));
mems(1)=mem;
Hello Jean-Yves,
Yes, you are right, it does look like a memory leak: the memory
increases linearly with the number of iterations (see attached file and
modified script below).
But keep in mind that the plot might integrate some growing overhead due
to the plotting...
Antoine
/
On 01/03/2021 09:06, Stéphane Mottelet wrote:
Hi Frederico,
I do not have any problem with the variable scoping in Scilab and as I
said before, even in Julia there is a similar scoping (at least for
the particular case of functions). However, the status of formal input
and output
Hello Clément,
I forgot that detail.
But this will not help Andrei use parallel_run, as it does not work
under linux, right?
Cheers,
Antoine
On 25/02/2021 16:10, Clément David wrote:
Hello Andrei,
To launch the Scilab 5.5.2 binary on new Linux version, you might need
to remove some
Hello all,
On 22/02/2021 10:12, Stéphane Mottelet wrote:
Hi,
Le 22/02/2021 à 09:43, Clément David a écrit :
Hello all,
Thanks for opening the discussion on this “new user”-related topic,
this is always good to improve our help for existing user and new
comers ; to let them havie a clear
Hello Andrei,
I think this is a dead end.
As far as I remember, parallel_run only works on Windows, on 1 core and
is an ugly hack.
From https://help.scilab.org/doc/5.5.2/en_US/parallel_run.html :
"In this current version of Scilab, |parallel_run| uses only one core on
Windows platforms."
Hello Federico,
I agree with you that this would make more sense.
Could such a change be implemented for a point release?
I assume it would introduce some bugs in existing code relying on the
(unusual) double output...
Antoine
On 09/02/2021 03:24, Federico Miyara wrote:
Dear all,
I had
Hello Samuel,
Le 01/02/2021 à 23:26, Samuel Gougeon a écrit :
Dear all,
After having changed the default grid style in Scilab 6.1.0, i propose
to go on, tuning more carefully the default font size of axes labels.
Each time that i define a xlabel, ylabel or sometimes zlabel, and a
title,
me too!
Antoine
On 22/01/2021 22:11, P M wrote:
Yes, I did receive that message.
Best Regards,
Philipp
Am Fr., 22. Jan. 2021 um 21:05 Uhr schrieb Samuel Gougeon
mailto:sgoug...@free.fr>>:
Hello,
Has anyone received the recent message archived @
Hello Frederico,
Like Christophe, I am not sure this has anything to do with the
implementation of sin().
It seems to be a known limitation of numerical calculations using
floating numbers.
In particular, even with en hypothetical ideal value of %pi, because of
the conversion to a double,
On 31/12/2020 15:43, Samuel Gougeon wrote:
Le 31/12/2020 à 15:27, Antoine Monmayrant a écrit :
.../...
I am not sure that implementing the Julia solution with LaTeX would
improve a lot the situation:
* first, we still have to remember a code, the latex one ; this is
simple
On 31/12/2020 13:44, Samuel Gougeon wrote:
Le 31/12/2020 à 10:36, Antoine Monmayrant a écrit :
On 29/12/2020 16:39, Samuel Gougeon wrote:
As well, i must confess that having a ALT+X or any other keys
shortcut able to convert a series of 2 to 4 input unicodes to the
corresponding character
On 29/12/2020 16:39, Samuel Gougeon wrote:
As well, i must confess that having a ALT+X or any other keys shortcut
able to convert a series of 2 to 4 input unicodes to the corresponding
character -- as proposed in wish #16505 -- would be of almost no help
to me, because i do not remember
On 19/12/2020 16:24, Samuel Gougeon wrote:
Le 16/12/2020 à 14:16, Antoine Monmayrant a écrit :
That's the very first thing we change after installing scilab on all
the computers in our group, so I agree we need to change it.
I conclude that 512 MB is enough. Otherwise you would not have
18:58, Samuel Gougeon a écrit :
Le 03/12/2020 à 09:59, Antoine Monmayrant a écrit :
Hello again,
Just to add to my previous message: increasing nx or ny in my script
can crash scilab during the call to xend().
On my small local machine, this occurs for:
nx=4000;
ny=3000;
for which
Ah, and of course, there is a stupid bug in one of my functions!
A virtual croissant to the first one to spot it!
Antoine
PS: BTW, it's one of the errors that should be easy to catch with a
proper argument highlighting...
On 09/12/2020 15:09, Antoine Monmayrant wrote:
Hi all,
Scilab can
Hi all,
Scilab can use unicode characters (at least some) as variable names.
However, this does not play well with Scinotes syntax highlighting in
functions.
In particular, input/output arguments are no longer highlighted and
local line number inside the function does no longer work as
On 03/12/2020 02:10, TanCL wrote:
Hi, my previous message seems like not able to get posted due to some reason,
just to add some comment on this, I think the functions with same name under
2 different modules could be possibly called by:
That is exactly how things are working in Ada:
ou confirm this bug?
Antoine
On 03/12/2020 09:48, Antoine Monmayrant wrote:
Hello all,
In these days of remote working, I need to use again scilab in
headless mode to generate graphics.
In other words, I connect in command line only to a remote server
where scilab is installed and I want it t
Hello all,
In these days of remote working, I need to use again scilab in headless
mode to generate graphics.
In other words, I connect in command line only to a remote server where
scilab is installed and I want it to generate graphics using a
combination of driver, xinit and xend.
Thank you all, I mixed up filesep() & pathsep().
Antoine
On 27/11/2020 09:58, Stéphane Mottelet wrote:
It’s the char to separate paths in the PATH environment variable.
Different from filesep().
S.
Le 27 nov. 2020 à 09:55, Antoine Monmayrant
a écrit :
Hello all,
I just f
Hello all,
I just found this today, on a linux machine (scilab 6.1.0 ubuntu 18.04 LTS):
--> pathsep()
ans =
":"
it definitely sounds like a bug to me, no?
As anyone else experience some issues with pathsep ?
Cheers,
Antoine
___
t, I will provide an example.
Stefan
On 2020-10-18 10:10, Antoine Monmayrant wrote:
Even If you cannot measure the issue, if you have a minimum working
example that triggers this bug, it would be helpful to share it with
us so we can try to reproduce the issue and maybe link it to some
ver
Even If you cannot measure the issue, if you have a minimum working
example that triggers this bug, it would be helpful to share it with us
so we can try to reproduce the issue and maybe link it to some version
of java or your os.
By the way, did you try to take another computer and do a
On 17/10/2020 21:00, Stefan Du Rietz wrote:
Hello Stephane and Antoine,
I tried to explain why I cannot. After I have pressed the button with
the callback, I can see that it takes a long time until the toc()
message from the start of myfunction arrives. I don't know how to get
the time from
Le 07/10/2020 à 04:24, jaipur a écrit :
Hello,
Following your suggestion, gce().clip_state = 'off' could succeed zoom in.
While I continue to zoom in to watch the detail of a hill top, the top is
clipped by another something.
Could someone teach me the cause of this clipping and how to avoid
On 01/10/2020 09:05, Dang Ngoc Chan, Christophe wrote:
Hello,
De la part de P M
Envoyé : mercredi 30 septembre 2020 16:50
exact dot-coordinates, drawn as filled circles.
All pixel coordinates of such an area would have to have exactly one single
pixel value.
The resulting graphic right now
Hello all,
Just wondering what is the normal way to save graphics nowadays.
I just had a look at 'help xsave' to see whether it is deprecated or
whether this is the official way to do it.
This page reads:
"For graphics xsave(file_name,win_num) use preferably
save(file_name,scf(win_num))."
Hello all,
During teaching, I usually run a bunch of scilab demos using "scilab -f
demofile1", "scilab -f demofile2", etc ...
Sadly, every call to "scilab -f file" opens a new instance of scilab.
Is this possible to reuse an existing instance of scilab?
Or even better: reuse an instance of
On 15/09/2020 07:32, Samuel Gougeon wrote:
Le 14/09/2020 à 16:14, Antoine Monmayrant a écrit :
Hello all,
For some reason, I don't understand the output of:
plot(rand(1:10),':')
This should be a 'dotted line', as explained on the page:
https://help.scilab.org/docs/6.1.0/en_US
Le 14/09/2020 à 16:23, Heinz Nabielek a écrit :
I get a perfect dotted line.
What?
I tested this under linux (ubuntu 18.04) & Windows10, with both 5.5.2
and the 6.1 and I don't get a dotted line...
I attached the output of:
scf();plot(1:10,':')
Antoine
Hello all,
For some reason, I don't understand the output of:
plot(rand(1:10),':')
This should be a 'dotted line', as explained on the page:
https://help.scilab.org/docs/6.1.0/en_US/LineSpec.html
But I get a line_style==5 which is some kind of 1dash-2dots line.
Looking at what's on
On 27/08/2020 17:55, Dang Ngoc Chan, Christophe wrote:
Hello,
De : Antoine Monmayrant
Envoyé : jeudi 27 août 2020 17:25
n=real(n);
Now it works.
Basic.
I thought about this and I know I tested some isreal(sellmeier(lambda)) stuff
during the development but I did not thought it would
OK, forget my previous answer.
Use this:
function [n] = sellmeier(KL, lambda)
K1 = KL(1); K2 = KL(2); K3 = KL(3);
L1 = KL(4); L2 = KL(5); L3 = KL(6);
lambdacarre = lambda.*lambda;
foo1 = lambdacarre - L1;
foo2 = lambdacarre - L2;
foo3 = lambdacarre - L3;
foo =
Hello,
I can tell you what happened: for some values of lambda and some values
of K(4,5,6), your function is undefined and the leastsq goes kaboom!
It is never a good idea to fit a function that can become undefined for
some parameters/xvalues.
Try to redefine the function you fit to avoid
Hello Pierre,
Exactly like last time, its seems to be Windows10-specific as your
script does work as expected under Linux.
Antoine
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users
Hello,
It seems to be Windows specific as your script works as expected under
linux:
ls /tmp/SCI_TMP_21007_Y24sfl/
Test ùùééêë.scg Test ùùééêë.txt
Could this be some encoding issues?
Antoine
Le 26/08/2020 à 09:28, Perrichon a écrit :
Rep=TMPDIR
chdir(Rep)
Name=Rep + "\Test ùùééêë"
On 21/08/2020 09:38, perrichon.pie...@wanadoo.fr wrote:
Hello Federico
Enter « abort » on your keyboard
Or "resume", depending on what you want to do and how you arrived here.
Adding some "pause" inside some buggy function is the most basic way of
debugging: the -1-> prompt gives access to
Hello Heinz,
Please see the attached tutorial¹ I wrote for the other physicists in my
lab on how to use scilab to fit data with a model and calculate the
confidence interval.
The reference paper mentioned in the comments is worth reading, it
helped me a lot understanding how the confidence
Hello,
It works as expected here (6.1.0 under linux).
Is this an encoding issue?
It looks like all the spaces are replaced by Âs...
Antoine
Le 19/08/2020 à 00:10, Heinz Nabielek a écrit :
--> calendar
AugÂ2020
MonÂÂTueÂÂWedÂÂThuÂÂFriÂÂSatÂÂSun
Hello Adrian,
Here is what I would do:
(1) use 'tag' property field of your curve together with findobj to get
access to the plot to be updated, without passing the handle.
(2) instead of deleting the curve and recreating it, I would directly
modify its content (data property) and then ask
From: Antoine Monmayrant
To: P M
Hello Philipp,
I played a bit with tiff format a while ago (as none of the image
processing toolboxes could be installed on my work computers).
The long story short: one of our microscope is storing data in a format
(*.ols) that is just tiff file
> malloc_error_break to debug
>
> Same crash with Scilab-branch-6.1 under Ubuntu 18.04, with 128Gb ram:
>
> "a28=[1:2^28];"
> ATTENTION : Option -v7 ajoutée.
>
> "savematfile('a28.mat','a28');"
> Segmentation fault (core dumped)
>
> Again, it is not clear why you just do not fuse all data together into one
> matrix and use plot2d() to plot all data at once.
>From my own experience, this might be the case when you want to track the
>progression of a lengthy calculation: you periodically add the new data on top
>of the
45x645 constant] [645x645x645 constant]
Maybe the structure I tried is too simple (just two hypermatrices in a
cell) so please give us a representative failing example.
S.
Le 17/06/2020 à 13:22, Antoine Monmayrant a écrit :
Hello All,
I cannot open large matfile in scilab (~3.4Gb).
Scilab is
On 17/06/2020 13:51, Stéphane Mottelet wrote:
Hello Antoine,
Did you to save a single "hypermatrix in a cell" in matlab and then
load in Scilab ?
No, just the hypermatrix, not a cell containing only one hypermatrix.
S.
Le 17/06/2020 à 13:22, Antoine Monmayrant a écrit :
Hel
Hello All,
I cannot open large matfile in scilab (~3.4Gb).
Scilab is always dying with an error message that is extremely
instructive: "Killed".
It's a bit cumbersome to share this big fie, so do you have any idea on
how to investigate this issue and try to locate the root cause?
As a side
On 05/06/2020 14:48, Stéphane Mottelet wrote:
Hello all,
As you may have noticed, there is now a little game in the
Gaphics/Animation section of the demonstrations. As the speed and
responsiveness seems to be similar under all platforms, it would be
funny to launch a little contest. In the
gce().data.
This makes the three .svg .pdf and .ps conversions working.
Best regards.
Samuel
Le 27/05/2020 à 08:58, Antoine Monmayrant a écrit :
Hi all,
It seems there is a bug in the export of graphics to vector formats
(svg, pdf, ps): it fails for elements in your graphic windows that
were gener
he Matplot() instruction, without adding a fourth
layer to gce().data.
This makes the three .svg .pdf and .ps conversions working.
Best regards.
Samuel
Le 27/05/2020 à 08:58, Antoine Monmayrant a écrit :
Hi all,
It seems there is a bug in the export of graphics to vector formats
(svg, pdf, ps)
Hi all,
It seems there is a bug in the export of graphics to vector formats
(svg, pdf, ps): it fails for elements in your graphic windows that were
generated using Matplot on an RGB hypermatrix:
cult to use if you are already familiar with the scilab one.
You could try from python to assess whether you are trying to do
something inherently wrong or whether it's a bug in scilab.
Paul
Le dim. 24 mai 2020 à 14:38, Antoine Monmayrant
mailto:antoine.monmayr...@laas.f
Hello Paul,
This is not a solution, but just tests to assert that the problem does
come from scilab and not from your datasets.
(1) Can you try to use command-line tool h5copy (that comes with the
hdf5-tools pacakge on a Debian/Ubuntu Linux distribution) to do it
outside of scilab?
If you
Hello Paul,
You want to keep "unique" values along the first column of M.
Here is how you can get this result:
//
M = [ 0 2; 0 6; 1 8;2 9]
firstCol=M(:,1);
[dum,ind]=unique(firstCol);
MuniqueFirstCol=M(ind,:);
//
On 12/05/2020 10:20, Daniel Stringari wrote:
Good Morning,
The file exists ... Every time the code is run, it tries to create a
series of files inside the address "C: \ Temp \ PGC \ ..." using the
functions FULLFILE, CSVWRITE, CSVREAD and MDELETE to create and
manipulate the data. This tool
Hello Daniel,
It seems to me that the error is more the absence of the file
"C:\Temp\PGC\Sai_Lot1v3.txt".
You can try to check just before line 206 whether the file is present or
not:
ls("C:\Temp\PGC\Sai_Lot1v3.txt") or isfile("C:\Temp\PGC\Sai_Lot1v3.txt") .
Hope it helps,
Antoine
On
Hello,
I am not sure to understand what you want to achieve here.
It is not really clear for me.
You might be able to hack something using 'exists" but I am not sure
that it would fit nicely with the way Scilab is designed...
Antoine
On 07/05/2020 14:01, kjubo wrote:
Dear all,
I would
. the Ubuntu packages do NOT work. I will try
downloading from Scilab.org.
Thank you for your suggestion!
Jeff
On Wed, May 6, 2020 at 6:12 AM Antoine Monmayrant
mailto:antoine.monmayr...@laas.fr>> wrote:
Hello Jeff,
It seems I have the same problem (see below).
I just don
OK, I can confirm that the same bug is present in
ubuntu 18.04
ubuntu 20.04
pop_os 20.04
Antoine
On 06/05/2020 11:17, Antoine Monmayrant wrote:
Hello,
It seems to be the same issue than for ubuntu 18.04: the packaged
version of scilab is just not working.
You should download the last
Hello,
It seems to be the same issue than for ubuntu 18.04: the packaged
version of scilab is just not working.
You should download the last version of scilab (
https://www.scilab.org/download/6.1.0/scilab-6.1.0.bin.linux-x86_64.tar.gz
), untar it and launch it.
Hope it helps,
Antoine
On
b this way:
SCI_DISABLE_TK=1 SCI_JAVA_ENABLE_HEADLESS=1
_JAVA_OPTIONS='-Djava.awt.headless=true' bin/scilab-adv-cli
You will be able to use graphic commands (without visible output) and
then export directy with e.g. xs2pdf.
S.
Le 29/04/2020 à 14:51, Antoine Monmayrant a écrit :
Hello All,
Here is
On 29/04/2020 15:18, Stéphane Mottelet wrote:
SCI_DISABLE_TK=1 SCI_JAVA_ENABLE_HEADLESS=1
_JAVA_OPTIONS='-Djava.awt.headless=true'
Thanks Stéphane for this dark magic!
It works.
Is this documented somewhere?
Antoine
___
users mailing list
Hello All,
Here is a Covid19 & forced remote work issue.
One of my students has to run some of his simulations and generate
png/svg figures on a linux workstation we don't have physical access to
given the current lockdown.
The problem is that from his Windows laptop without X server, he
<http://www.hidglobal.com/>
Unit 3, Cae Gwyrdd,
Green meadow Springs,
Cardiff, UK,
CF15 7AB.
www.hidglobal.com <http://www.hidglobal.com>
*From:*users *On Behalf Of *Antoine
Monmayrant
*Sent:* 27 April 2020 16:41
*To:* Users mailing list for Scilab
*Subject:* [EXT] [Scilab-users] parsing
e :* users [users-boun...@lists.scilab.org] de la part de Antoine
Monmayrant [antoine.monmayr...@laas.fr]
*Envoyé :* lundi 27 avril 2020 17:40
*À :* Users mailing list for Scilab
*Objet :* [Scilab-users] parsing TSV (or CSV) file with scilab is a
nightmare
Hi all,
This is both a rant and des
Hi all,
This is both a rant and desperate cry for help.
I'm trying to parse some TSV data (tab separated data file) with scilab
and I cannot find a way to navigate around the minefield of bugs present
in meof/mgetl/mgetstr/csvRead.
A bit of context: I need to load into scilab data generated
Hi all,
I'm testing the newly released LTS for Ubuntu (20.04) and scilab does not work
out of the box.
I reported the bug here: https://bugzilla.scilab.org/show_bug.cgi?id=16418
Cheers,
Antoine
___
users mailing list
users@lists.scilab.org
, do you think you could fill a bug report?
Cheers,
Antoine
Le Vendredi, Avril 10, 2020 16:17 CEST, Claus Futtrup a
écrit:
>
> HA HA :-D ... it's funny!
>
> Cheers,
> Claus
>
> On 10.04.2020 16:09, Antoine Monmayrant wrote:
> > OK, I think I
OK, I think I nailed it:
function a()
if % then
end()
end
endfunction
It's the "end()" in "legend()" that sends the parser off the trail: it thinks
that the if block is over (as it has found "if", "then" & leg"end"() ) and then
treats the next "end" as matching the "function"
Futtrup a
écrit:
> Hi Scilabers
>
> Good examples are worth a lot. Maybe this one could be part of the
> Scilab documentation?
>
> Best regards,
> Claus
>
> On 06.04.2020 08:17, Antoine Monmayrant wrote:
> > Hello Heinz,
> >
> > See below the small e
Hello Heinz,
See below the small example I built and I refer to whenever I need to do some
data fitting with confidence intervals for the parameters of the model.
It is far from perfect but it might help you untangle the Jacobian and
covariance matrix thingy.
Just two words of caution: (1) I am
Hello,
I also ran some tests and it seems that the regression is clearly line-based:
ie the regression is worse for vector than for matrix because there more lines
to print to display a vector than a matrix of similar length.
See my test code below.
n1=300;
n2=100;
mat=rand(n1,n2);
tn=[];
/*
Hi again,
Just tested using the cli (no window, no java): it's even more : 0.34s vs 46s.
Antoine
Le Lundi, Mars 30, 2020 11:56 CEST, Federico Miyara
a écrit:
>
> Dear All,
>
> I have observed that Scilab 6.1 seems to have a regression respect to
> 6.0.2. Sometimes one forgets to put
Hello Frederico,
I can confirm this (6.0.2 vs 6.1) on linux Ubuntu 18.04 64bits:
6.0.2 -> ~1s
6.1.0 -> ~50s
Could you fill a bug report?
Antoine
Le Lundi, Mars 30, 2020 11:56 CEST, Federico Miyara
a écrit:
>
> Dear All,
>
> I have observed that Scilab 6.1 seems to have a
1 - 100 of 403 matches
Mail list logo
