Re: [Scilab-users] Scilab 6.0.2 is released!

[amonmayr]

Hi all,

Thanks for the good work, the list of bug fixes is quite impressive and 
I am happy to see among them some nasty bugs that were really annoying 
for me.
Sadly, http://bugzilla.scilab.org/show_bug.cgi?id=15336 is still present 
(scilab crashes right away on many ubuntu linux machines due to opengl 
driver issues).

The workaround it quite simple
    export MESA_GL_VERSION_OVERRIDE=3.0 ; scilab
and easy to apply.
But it's a terrible first experience for new users and, as the local 
scilab advocate, I can tell you that for many people it's enough to let 
them drop the ball and install matlab...


Cheers,

Antoine

Le 14/02/2019 à 18:09, yann.deb...@scilab-enterprises.com a écrit :

Dear Scilab users,

First of all, Happy valentine's day ❤️ You might say that we are 
romantic... as we are releasing Scilab 6.0.2 at the anniversary date 
of the release of Scilab 6.0.1 (14th of February 2018). But we are 
french after all!
This release was a joint effort between Scilab contributors and the 
Scilab team at ESI Group.


Scilab 6.0.2 is the second revision of the 6.0 development branch. It 
fixes up to 305 bugs and implements missing features from the 5.5.2 
version especially :


* fix crashes and buggy behaviors on functions, displays and error 
reporting.

* Xcos edition should no longer stop, block or crash Scilab.
* Many help pages have been improved with new examples and rephrasing.

For the complete list of changes and bugs fixed, please take a look at 
the CHANGES   file.


Download this brand new version at https://www.scilab.org/download/6.0.2

Openly Yours
Yann for the Scilab Team
___
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] Unable to update ATOMS packages - Scilab 6.0.1

[amonmayr]

Le 18/10/2018 à 21:59, Pndsc a écrit :

Blank window - sometimes the buttons themselves arent displayed but will
spawn when the mouse cursor goes over them.

https://imgur.com/a/lxdokm1

OK, this really looks like a driver issue or a java out of memory issue.
You should increase the amount of memory dedicated to the java virtual 
machine: Edit->Preferences->General->Java Heap Memory

I think you need to restart scilab to apply the change.



Maybe the fix I proposed you (the export MESA_GL_VERSION_OVERRIDE=3.0 ;
) is not exactly what you need. Someone told me to try to limit the mesa
gl version to use, but the optimal value might be different for you. You
might try to experiment different values.

It seems that this might have been a superfluous thing - the nightly build
scilab is the one that gives me a libgfortran error and refuses to start.
Conventional 6.0.1 starts fine but doesnt display any graphs.




--
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



--
+++

 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] HDF5 save is super slow

[amonmayr]

Le 18/10/2018 à 15:00, Stéphane Mottelet a écrit :

Hello again,

Le 18/10/2018 à 14:56, Clément David a écrit :

Hi Antoine,

That one point, vec2var has been defined to pass some datatypes from 
Scilab "ast" (C++ side, data pointers, refcounted) to Scilab "scicos" 
(C, raw memory allocated once and passed around). Some data 
structures might not be handled correctly, I was even surprised that 
mlists worked correctly.


Scilab Struct (or Cell) are missing as they are more complex 
datatypes to serialize. Handle are even harder (as you need to list 
the properties somewhere). Feel free to take a look at the code [1],


[1]: 
https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/cgit.scilab.org/scilab/tree/scilab/modules/scicos/src/cpp/var2vec.cpp?h=6.0#n243
Why is the code for structs (lines 242--74)  commented out ? Is it 
broken or else ?
If var2vec() / vec2var() could be extended to provide a universal way to 
serialize / deserialize really any scilab variable, that would be really 
nice.

Could we make a SEP or fill a bug as a wish ?

Antoine



Cheers,
--
Clément

-Original Message-
From: antoine monmayrant 
Sent: Thursday, October 18, 2018 2:47 PM
To: Clément DAVID ; Users 
mailing list for Scilab 

Cc: Clément David 
Subject: Re: [Scilab-users] HDF5 save is super slow



Le 18/10/2018 à 14:09, Clément DAVID a écrit :

Hello,

My 2cents, this is probably a poor man’s approach but Xcos offers 
vec2var / var2vec functions that encode in a double vector any 
Scilab datatypes passed as arguments. The encoding duplicates the 
data in memory so there might be some overhead.

Er, I tried var2vec, but it does not work with structures:
--> typeof(t)
   ans  =
   st

--> var2vec(t)
var2vec: Wrong type for input argument #1: Double, Integer, Boolean, 
String or List type.


Arghh... so var2vec does not work for any datatype right?

Antoine
On my machine, I have these timings using the attached script 
(Antoine’s one edited):

save list of syslins: 1.361704
save list of vec[]: 0.056788
save var2vec(list of syslins): 0.014411

Discarding hdf5 groups creation is a huge performance win but remove 
any way to create clean hdf5 (eg. to address subgroups directly).


Thanks,

--
Clément

From: users  On Behalf Of Arvid Rosén
Sent: Tuesday, October 16, 2018 1:01 PM
To: antoine.monmayr...@laas.fr; Users mailing list for Scilab

Subject: Re: [Scilab-users] HDF5 save is super slow

From: users
mailto:users-boun...@lists.scilab.org>

on behalf of "amonm...@laas.fr"

mailto:amonm...@laas.fr>>
Reply-To:
"antoine.monmayr...@laas.fr"
mailto:antoine.monmayr...@laas.fr>>, Users
mailing list for Scilab
mailto:users@lists.scilab.org>>
Date: Tuesday, 16 October 2018 at 09:53
To: "users@lists.scilab.org"
mailto:users@lists.scilab.org>>
Subject: Re: [Scilab-users] HDF5 save is super slow

Couldn't you create your own atom package that restore this raw 
memory dump for scilab 6.0?
I understand why we moved away from this model, but it seems to be 
key for you.
There is always a trade-off between portability (and robustness) and 
raw speed...


Yeah, if that was possible, I would certainly do it. We already have 
a bunch of C/C++ binaries that we compile and link dynamically, but 
for that to be easy to implement, I guess the lists and structures 
need to be stored linearly in one consecutive chunk of memory. I 
don’t know if that is the case. Anyone? C++ integrations and 
gateways are very poorly documented at the moment.
Otherwise, I would need to do some recursive implementation, that 
handles a bunch of different object types. Sounds painful.


Cheers,
Arvid

___
users mailing list
users@lists.scilab.org
https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/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] Unable to update ATOMS packages - Scilab 6.0.1

[amonmayr]

Le 16/10/2018 à 23:26, Pndsc a écrit :

Hi Antoine,

I gave this another go today, doing a fresh reinstall of Kubuntu 18.04 and
installing scilab using sudo as the very first thing I did after a sudo
apt-get upgrade. The same issue persists with ATOMS after doing this.

Following the installation instructions using wget for the 6.0.1 and nightly
build zips gave me multiple java errors ("Scilab cannot create Scilab Java
Main-Class" and X11GLXDrawableFactory issues) and a completely (instead of
"only" partially) install.
Can you give me the details of the error log in the console for this 
version?

Could it be a problem with the video drivers and mesa?
I had this issue at some point.
Could you try to use:

export MESA_GL_VERSION_OVERRIDE=3.0 ; /path/to/scilab-nightly/bin/scilab

instead of

 /path/to/scilab-nightly/bin/scilab

?

It solved my problems for a while.
No with some later updates, I no longer have this driver issue¹.

Hope it helps,

Antoine
¹ By the way, matlab suffer exactly the same problem on my machine, and 
I used the very same fix.


I've even done the above with 5.5.2 hoping that the issues would be resolved
with the earlier version.

I'm fresh out of ideas and can only think that maybe it has something to do
with my computer using a Ryzen 1700 processor.

I cant lie, I am bitterly disappointed that Scilab appears to be broken in
this manner.




--
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



--
+++

 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] HDF5 save is super slow

[amonmayr]

Le 15/10/2018 à 18:17, Arvid Rosén a écrit :


Hi again,

I just filed a bug report here:

http://bugzilla.scilab.org/show_bug.cgi?id=15809

Would it be possible to bring back the old mem-dump approach in scilab 6?

Couldn't you create your own atom package that restore this raw memory 
dump for scilab 6.0?
I understand why we moved away from this model, but it seems to be key 
for you.
There is always a trade-off between portability (and robustness) and raw 
speed...


I mean, could I write a gateway that just takes a pointer to the first 
byte in memory, figures out the size, and dumps to disk? Or maybe it 
doesn’t work like that. Writing a JSON exporter for storing filter 
coefficients in a math software package seems a bit ridicules, but 
hey, if it works it might be worth it in our case.


I was also wondering whether this can be done in HDF5: ie do some 
serialization of your structure and dump it in hdf5?
We use hdf5 for Labview and for some horrible structures (like arrays of 
clusters containing lots of elements of different types), we just turn 
them into byte stream and dump the stream in an hdf5 dataset.

We then retrieve it and rebuild the structure (knowing its shape).
Could this be implemented in Scilab 6?
What could be missing, the any variable -> bytestream conversion and the 
way back?


Antoine


Cheers,

Arvid

*From: *users  on behalf of Clément 
DAVID 

*Reply-To: *Users mailing list for Scilab 
*Date: *Monday, 15 October 2018 at 15:48
*To: *Users mailing list for Scilab 
*Cc: *Clément David 
*Subject: *Re: [Scilab-users] HDF5 save is super slow

Hello all,

Correct, I experienced such a slowness while working with Xcos 
diagrams for Scilab 5. At first we considered HDF5 for this deep 
nested list / mlist data-structure storage however after some tests ; 
XML might be used for tree-like storage and HDF5 (or Java types 
serialization) for big matrices.


AFAIK currently there is no easy way to load/save specifying a format 
other than HDF5 ; maybe adding xmlSave/xmlLoad sci_gateway to let the 
user select an xml file format for any Scilab structure might provide 
better performance on your use-case. JSON might also be another 
candidate to look at for decent serialization support.


PS: Scilab 5.5.1 load/save are direct memory dump so this is really 
the fastest you can get from Scilab ; HDF5 binary format is good 
enough for matrices


--

Clément

*From:*users  *On Behalf Of *Stéphane 
Mottelet

*Sent:* Monday, October 15, 2018 2:36 PM
*To:* users@lists.scilab.org
*Subject:* Re: [Scilab-users] HDF5 save is super slow

Hello,

I looked a little bit in the sources: the evident bottleneck is the 
nested creation of an hdf5 group each time that a container variable 
is met.
For the given example, this is particularly evident. If you replace 
the syslin structure by the corresponding [A,B;C,D] matrix, then save 
is ten times faster:


N = 4;
n = 1000;
filters = list();
for i=1:n
  G=syslin('c', rand(N,N), rand(N,1), rand(1,N), rand(1,1));
  filters($+1) = G;
end
tic();
save('filters.dat', 'filters');
disp(toc());
--> disp(toc());

   0.724754

N = 4;
n = 1000;
filters = list()
for i=1:n
  G=syslin('c', rand(N,N), rand(N,1), rand(1,N), rand(1,1));
  filters($+1) = [G.a G.b;G.c G.d];
end
tic();
save('filters.dat', 'filters');
disp(toc());
--> disp(toc());

   0.082302

Serializing container objects seems to be the solution, but it goes 
towards an orthogonal direction w.r.t. the hdf5 portability spirit.


S.


Le 15/10/2018 à 12:22, Antoine Monmayrant a écrit :

Le 15/10/2018 à 11:55, Arvid Rosén a écrit :

Hi,

Thanks for getting back to me!

Unfortunately, we used Scilab’s pretty cool way of doing
object orientation, so we have big nested tlist structures
with multiple instances of various lists of filters and other
structures, as in my example. Saving those structures in some
explicit manual way would be extremely complicated. Or is
there some way of writing explicit HDF5 saving/loading schemes
using overloading? That would be great! I am sure we could
find the main culprits and do something explicit for them, but
as they can be located wherever in a big nested structure, it
would be painful to do anything on the top level.

Another, related I guess, problem here is that the new file
format uses about 15 times as much disk space as the old
format (for a typical ill-behaved nested structure). That adds
to the save/load time too I guess, but is probably not the
main source here.

Argh, yes, I tested it and in your example, I have a file x8.5 bigger.
I think that both increases in time and size are real issues and
should be reported as bugs.

By the way, I rewrote your script to run it under both 6.0 and 5.5:

/
N = 4;
n = 1;
filters = list();

for i=1:n
  G=syslin('c', 

Re: [Scilab-users] HDF5 save is super slow

[amonmayr]

Hello Arvid,

On m

Le 15/10/2018 à 10:11, Arvid Rosén a écrit :


/

N = 4;

n = 1;

filters = list();

for i=1:n

  G=syslin('c', rand(N,N), rand(N,1), rand(1,N), rand(1,1));

  filters($+1) = G;

end

tic();

save('filters.dat', filters);

ts1 = toc();

tic();

save('filters.dat', 'filters');

ts2 = toc();

printf("old save %.2fs\n", ts1);

printf("new save %.2fs\n", ts2);

printf("slowdown %.1f\n", ts2/ts1);

/



--
+++

 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] HDF5 save is super slow

[amonmayr]

Hello,

I tried your code in 5.5.1 and the last nightly-build of 6.0: I see a 
slowdown of around 175 between old save in 5.5.1 and new (and only) save 
in 6.0.
It's really related to the data structure, because we use hdf5 
read/write a lot here and did not experience significant slowdowns using 
6.0.
I think the overhead might come to the translation of your fairly 
complex variable (a long array of tlist) in the corresponding hdf5 
structure.

In the old save, this translation was not necessary.
Maybe you could try to save your data in a different way.
For example:
3) you could save each element of "filters" in a separate file.
2) you could bypass save and directly write your data in a hdf5 file by 
using h5open(), h5write() directly. It means you need to write your own 
load() for your custom file format. But this way, you can try to find 
the best way to layout your data in hdf5 format.
3) in addition to 2) you could try to save each entry of your "filters" 
array as one dataset in a given hdf5 file.


Did you search on bugzilla whether this bug was already submitted?
Could you try to report it?


Antoine

Le 15/10/2018 à 10:11, Arvid Rosén a écrit :


/

N = 4;

n = 1;

filters = list();

for i=1:n

  G=syslin('c', rand(N,N), rand(N,1), rand(1,N), rand(1,1));

  filters($+1) = G;

end

tic();

save('filters.dat', filters);

ts1 = toc();

tic();

save('filters.dat', 'filters');

ts2 = toc();

printf("old save %.2fs\n", ts1);

printf("new save %.2fs\n", ts2);

printf("slowdown %.1f\n", ts2/ts1);

/



--
+++

 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] Unable to update ATOMS packages - Scilab 6.0.1

[amonmayr]

Le 11/10/2018 à 23:33, Pndsc a écrit :

Hi Antoine,

Yes, I had tried the nightly version. Scilab continued to crash after
clicking the ATOMS package manager icon as before.

I've tried several times this evening to download another copy of one of the
nightly versions but there seems to be some kind of issue with the server
this evening - while I can view the downloads page any attempt to download
the nightly release fails on both the problem linux computer and my windows
alternate.

I'll give it another go tomorrow or over the weekend.

Thanks,

Chris.



--
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


Hello Chris,

I just tried scilab in Kubuntu 18.04.
I installed kubuntu-full in a Ubuntu 18.04 virtual machine, then scilab 
from the ubuntu repos and atoms worked without any problem.


Could you try to purge scilab, remove the content of SCIHOME (something 
like ~/.Scilab/scilab-6.0.1) and reinstall from scratch?


Antoine

--
+++

 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] grand in 6.0.1

[amonmayr]

Le 11/10/2018 à 19:57, Adelson Oliveira a écrit :

Hello,

It seems that there is a problem with grand in scilab 6.0.1. It used 
to work in 6.0 but now one gets,


--> grand(10,1,"nor",0,1)

An error has been detected while loading 
/u/s0b6/Baixas/SCILAB/scilab-6.0.1/share/scilab/modules/randlib/.libs/libscirandlib.so: 
/u/s0b6/Baixas/SCILAB/scilab-6.0.1/share/scilab/modules/randlib/.libs/libscirandlib.so: 
undefined symbol: _gfortran_string_index


BTW, libscirandlib.so in 6.0.1 is found at SCI_HOME/lib! The 
directories listed above are empty or do not exist.

Hello again,

I just tried grand(10,1,"nor",0,1) on a fresh install of 6.0.1 on Ubuntu 
18.04 and I can reproduce your bug.

Can you fill a bug report on bugzilla?

Antoine


Thanks


___
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] Unable to update ATOMS packages - Scilab 6.0.1

[amonmayr]

Le 10/10/2018 à 23:37, Pndsc a écrit :

So to update my own inquiry - as far as I can make out theres no solution to
this problem. Or at least, I havent been able to fix it.

Hello,

Did you try using the last nightly from the 6.x-branch, like I suggested 
two days ago?


https://www.scilab.org/en/development/nightly_builds/branch60

Did it work?
If it worked, it means this is not an unsolved problem, it is just a 
matter of getting this fix to an official scilab release and wait for it 
to be packaged by your distro.


Cheers,

Antoine


I'm not the only person with this problem - theres an  Ubuntu stackexchange
thread with a suggested fix here

by N0rbert which might prove useful for other people with issues of simply
getting Scilab to work, but does not solve my issue of ATOMS not updating or
displaying an up to date package list.

The HDF5 thing is a known issue and is on the bugtracker here thanks to
N0rbert:

https://bugs.launchpad.net/ubuntu/+source/scilab/+bug/1765503

I have to admit I have a hard time with believing that this issue has been
allowed to persist for so long with the current most widespread linux
distribution out there.

Running an atomsInstall command doesnt work either:

--> atomsInstall("coselica")
Scanning repository http://atoms.scilab.org/6.0 ... Done

at line   265 of function atomsDESCRIPTIONget (
/usr/share/scilab/modules/atoms/macros/atoms_internals/atomsDESCRIPTIONget.sci
line 284 )
at line31 of function atomsIsPackage  (
/usr/share/scilab/modules/atoms/macros/atoms_internals/atomsIsPackage.sci
line 47 )
at line69 of function atomsInstallList(
/usr/share/scilab/modules/atoms/macros/atoms_internals/atomsInstallList.sci
line 108 )
at line   233 of function atomsInstall(
/usr/share/scilab/modules/atoms/macros/atomsInstall.sci line 249 )

atomsDESCRIPTIONget: save
('/home/chris/.Scilab/scilab-6.0.1/.atoms/packages') has failed.

I dont know if its significant or not, but in
/usr/share/scilab/modules/atoms/etc/ , in the "repositories" text file, the
url for the atoms repository for 6.0 (https://atoms.scilab.org/6.0/) returns
a 443 forbidden error.

Its late here but the next thing on my list to do tomorrow is to download
the package zips manually and installing via atomsInstall('pathtozip').



--
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



--
+++

 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] Re : fftshift and ifftshift are way too different

[amonmayr]

Le 10/10/2018 à 08:47, Samuel Gougeon a écrit :

Le 09/10/2018 à 21:52, antoine monmayrant a écrit :

Hello Samuel,

Sorry I might not have made myself clear: fft and fftshift provide 
the ability to perform transform along only one of the dimensions of 
a multidimensional array.
Something like S(x,y,z) --[FFT along 3rd dim]--> 
ffthift(ffft(S(x,y,z), -1,3),3)=Ŝ(x,y,kz).
In that case, you need to perform fft and eventually fftshift along 
only the dimension of the transform.
ifftshift should also provide the same possibility to perform the 
inverse transform: Ŝ(x,y,kz) --[IFFT along 3rd dim]--> 
iffthift(ffft(Ŝ(x,y,kz), +1,3),3)=S(x,y,z).


This is a basic signal processing requirement in my field.


Hello Antoine,

Yes, you are right: in case of directional FFT and odd number of 
elements along the chosen direction, ifftshift can't presently be used.
Could you please post the same remark on bugzilla? This bug/wish is 
not yet reported.

Done: http://bugzilla.scilab.org/show_bug.cgi?id=15799


IMO we may propose and include it in Scilab as soon as for Scilab 6.0.2.

BTW, still IMO, fftshift and ifftshift should rather be merged in a 
single function.
It's the same code, except a floor<=>ceil. This should deserve just an 
option, not a separate dedicated function.
I guess that this separation likely comes from a kind of abusive 
Matlab-like mimicry.


Best regards
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] Re : fftshift and ifftshift are way too different

[amonmayr]

Le 10/10/2018 à 08:47, Samuel Gougeon a écrit :

Le 09/10/2018 à 21:52, antoine monmayrant a écrit :

Hello Samuel,

Sorry I might not have made myself clear: fft and fftshift provide 
the ability to perform transform along only one of the dimensions of 
a multidimensional array.
Something like S(x,y,z) --[FFT along 3rd dim]--> 
ffthift(ffft(S(x,y,z), -1,3),3)=Ŝ(x,y,kz).
In that case, you need to perform fft and eventually fftshift along 
only the dimension of the transform.
ifftshift should also provide the same possibility to perform the 
inverse transform: Ŝ(x,y,kz) --[IFFT along 3rd dim]--> 
iffthift(ffft(Ŝ(x,y,kz), +1,3),3)=S(x,y,z).


This is a basic signal processing requirement in my field.


Hello Antoine,

Yes, you are right: in case of directional FFT and odd number of 
elements along the chosen direction, ifftshift can't presently be used.
Could you please post the same remark on bugzilla? This bug/wish is 
not yet reported.

OK, I'll put it in my TODO-list.


IMO we may propose and include it in Scilab as soon as for Scilab 6.0.2.

BTW, still IMO, fftshift and ifftshift should rather be merged in a 
single function.
It's the same code, except a floor<=>ceil. This should deserve just an 
option, not a separate dedicated function.
I guess that this separation likely comes from a kind of abusive 
Matlab-like mimicry.

Yes, I agree.
But I don't see how we can merge the two without increasing the huge 
halo of confusion that blurs the help pages and use of fft-related 
functions¹ ².
The first idea that came to my mind was to make one single fftshift 
function where:
 - if dim>0, you do direct shift (ie for a direct Fourier transform) 
along dimension dim;
 - if dim<0, you do inverse shift (ie for an inverse Fourier transform) 
along dimension |dim|.
But as "-1" means direct fft and "+1" inverse fft, mixing fft and 
fftshift would be a real mess.


Antoine
¹ One I just discovered yesterday: the help page for fft is not listed 
in "Scilab Help >> Signal Processing > Transforms " ! Only ifft is 
listed, cool, he? Of course, ifft points to "Scilab Help >> Signal 
Processing > Transforms > fft". Idem  for dst, ...

² Oh, and this one cool too: in the fft help page:
"incr
a vector of positive numbers with integer values, or a vector of 
positive integers. *See the Description part for details.*" but the 
Description never says what the heck "incr" is, does and means 
Arghhh. It only appears once in an example of a "previous syntax".




Best regards
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] csvRead hangs scilab for big csv file (more than 10000 lines)

[amonmayr]

Hi all,

I submitted a bug report with a test script and csv file: 
http://bugzilla.scilab.org/show_bug.cgi?id=15788

Could you try it  with your os/scilab-version and comment the bug report?

Cheers,

Antoine

Le 02/10/2018 à 09:36, antoine.monmayr...@laas.fr a écrit :

Hi,

I'm trying to load a big csv file ( 20002 lines).
It seems that scilab fails when I have more than 1 lines in my csv 
file.
If I try to csvRead the whole file, I have a spinning wait icon of 
death that stays there forever (I tried this night: it spinned for 
more than 17 hours).

The only way to recover is to kill scilab (Ctrl+C does not work).
If I split my file in several files with less than 1 lines, I can 
read each chunk in a matter of a few ms and concatenate them without a 
problem.

As anyone ever experienced such a problem with csvRead?


Antoine



--
+++

 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] [Scilab-Dev] algebra conventions with integer types to be discussed

[amonmayr]

Le 18/09/2018 à 20:53, Stéphane Mottelet a écrit :

Hello Philippe,

Great to hear from you,

Le 18/09/2018 à 19:26, philippe a écrit :

Le 17/09/2018 à 19:03, Stéphane Mottelet a écrit :
Do I have to conclude that the implementation is currently so 
incoherent

that *nobody* uses integer types in Scilab (other than Scilab code
itself) ?

it's a new feature, I would have like to use it  before ... I've build
my own solution and now I just need time replace it with int64.

For mixed int/double expression I expect to get the best floating point
approximation as a result.

and for int/int ?
For me, this should be int, to be consistent with most of the languages 
I use.

So 3.0/4.0=0.75 but 3/4=0.
But maybe getting a rational would make more sense?

Antoine


S.



Best regards,

Philippe


___
users mailing list
users@lists.scilab.org
https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users 



___
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] xload vs load

[amonmayr]

Hi all,

I found a way to reproducibly trigger the bug, and reported it here : 
https://bugzilla.scilab.org/show_bug.cgi?id=15765

Can you try the sample script on the example graphic file?

Cheers,

Antoine

--
+++

 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] Division of uint8 matrix by a double matrix => segfault in scilab-branch-6.0 ?

[amonmayr]

Le 10/09/2018 à 15:28, amonm...@laas.fr a écrit :

Le 10/09/2018 à 14:50, Stéphane Mottelet a écrit :

Le 10/09/2018 à 14:35, antoine.monmayr...@laas.fr a écrit :

Hello,


I think I found a bug in the current 6.0 branch:

a=uint8(rand(2,2)*255);
b=rand(2,2);
//let's be sure not to divide by 0
while or(b==0)
    b=rand(2,2);
end
//adios amigo: Segmentation fault (core dumped)
a./b

Dividing a uint8 matrix by a double matrix is always causing a 
segfault on my machine.

Can you reproduce this bug on your machine?
Does anyone know whether it's a known bug or not?

I have found : 
https://antispam.utc.fr/proxy/2/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/bugzilla.scilab.org/show_bug.cgi?id=15716 
but it is not exactly the same (I don't do any division by zero, 
just element-wise division.



Cheers,


Antoine


Hello Antoine,

Surely, this is a bug, but what type do you expect for the (eventual) 
result ?

I reported a bug: https://bugzilla.scilab.org/show_bug.cgi?id=15759
Can some or you try my test script for your OS/scilab version?
Weirdly enough, under scilab 5.5.2, there is no segfault, but scilab 
complains about a division by zero (whereas there is no division by 
zero).
Also, division (not element-wise division) gives a funny result, both 
for 5.5.2 and the current master:


a=uint8(rand(2,2)*255);
b=rand(2,2);
//let's be sure not to divide by 0
while or(b==0)
    b=rand(2,2);
end
//just a division :
// master and scilab-6.0 : Operator / : Error -1 not yet managed.
// 5.5.2 : !--error 26
//            Too complex recursion! (recursion tables are full)
//            at line   9 of function %i_r_i called by :   ...
a/b




Antoine


S.





--
+++

 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] Division of uint8 matrix by a double matrix => segfault in scilab-branch-6.0 ?

[amonmayr]

Le 10/09/2018 à 14:50, Stéphane Mottelet a écrit :

Le 10/09/2018 à 14:35, antoine.monmayr...@laas.fr a écrit :

Hello,


I think I found a bug in the current 6.0 branch:

a=uint8(rand(2,2)*255);
b=rand(2,2);
//let's be sure not to divide by 0
while or(b==0)
    b=rand(2,2);
end
//adios amigo: Segmentation fault (core dumped)
a./b

Dividing a uint8 matrix by a double matrix is always causing a 
segfault on my machine.

Can you reproduce this bug on your machine?
Does anyone know whether it's a known bug or not?

I have found : 
https://antispam.utc.fr/proxy/2/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/bugzilla.scilab.org/show_bug.cgi?id=15716 
but it is not exactly the same (I don't do any division by zero, just 
element-wise division.



Cheers,


Antoine


Hello Antoine,

Surely, this is a bug, but what type do you expect for the (eventual) 
result ?

I reported a bug: https://bugzilla.scilab.org/show_bug.cgi?id=15759
Can some or you try my test script for your OS/scilab version?
Weirdly enough, under scilab 5.5.2, there is no segfault, but scilab 
complains about a division by zero (whereas there is no division by zero).


Antoine


S.



--
+++

 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] Division of uint8 matrix by a double matrix => segfault in scilab-branch-6.0 ?

[amonmayr]

Le 10/09/2018 à 14:50, Stéphane Mottelet a écrit :

Le 10/09/2018 à 14:35, antoine.monmayr...@laas.fr a écrit :

Hello,


I think I found a bug in the current 6.0 branch:

a=uint8(rand(2,2)*255);
b=rand(2,2);
//let's be sure not to divide by 0
while or(b==0)
    b=rand(2,2);
end
//adios amigo: Segmentation fault (core dumped)
a./b

Dividing a uint8 matrix by a double matrix is always causing a 
segfault on my machine.

Can you reproduce this bug on your machine?
Does anyone know whether it's a known bug or not?

I have found : 
https://antispam.utc.fr/proxy/2/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/bugzilla.scilab.org/show_bug.cgi?id=15716 
but it is not exactly the same (I don't do any division by zero, just 
element-wise division.



Cheers,


Antoine


Hello Antoine,

Surely, this is a bug, but what type do you expect for the (eventual) 
result ?
I don't expect anything from this division, I don't think it makes much 
sense. :-)

I just don't expect scilab to die when someone writes something like that!
In fact, I discovered this bug while I was progressively changing the 
type of my variables from uint8 to double.
As a side note, when dividing a uint8() by a double() matlab returns a 
uint8(), which is not really intuitive to me.


Cheers,

Antoine


S.



--
+++

 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] hist3d & density plots

[amonmayr]

Le 10/09/2018 à 11:00, Stéphane Mottelet a écrit :

Le 10/09/2018 à 09:56, antoine.monmayr...@laas.fr a écrit :

Hi all,

I'm trying to plot the density of scatter points in (x,y).
Basically, I have a huge Xvec and a huge Yvec of same size that 
represents the position of a huge number of points in a 2D plane.
I would like to get a density plot, that is given a certain grid, a 
2D plot representing the number of scatter points within a each cell 
of the grid.

In matplotib, this corresponds to functions like "hist2d" and "hexbin".
Is there any equivalent in Scilab?
Or do I have to calculate by hand my density matrix and then use 
graplot or contourfill to plot my density?
Any pointer at the least inefficient way to do this calculation is 
more than welcome...


Thank you in advance for your help,


Antoine


Hello Antoine,

The most efficient at the Scilab level would be to use the incremental 
feature of "sparse":


function d=bins2d(x,y,xbins,ybins)
 n = size(x,"*");
    [ix,cx] = dsearch(x,xbins);
    [iy,cy] = dsearch(y,ybins);
    kin = find((ix>0) & (iy>0));
    d = full(sparse([ix(kin) iy(kin)], ones(kin), [size(xbins,"*")-1, 
size(ybins,"*")-1]));

end

x = rand(1,1,'normal');
y = rand(1,1,'normal');

--> d = bins2d(x,y,-5:5,-5:5)
 d  =

   0.   0.   0.    0. 1.  0.  0. 0.    0.   0.
   0.   0.   0.    3. 4.  4.  0. 0.    0.   0.
   0.   0.   6.    31.    82. 80. 31.    2.    0.   0.
   0.   0.   24.   183.   477.    477.    200.   25.   3.   0.
   0.   5.   68.   439.   1131.   1158.   426.   57.   4.   0.
   0.   5.   91.   485.   1168.   1220.   438.   72.   3.   0.
   0.   4.   30.   190.   470.    472.    173.   21.   3.   0.
   0.   0.   6.    30.    83. 78. 24.    2.    0.   0.
   0.   1.   0.    2. 2.  3.  3. 0.    0.   0.
   0.   0.   0.    0. 0.  0.  0. 0.    0.   0.


--> sum(d)
 ans  =

   1.

Thanks a lot, it works and is really fast even 2*10⁶ scatter points!


This feature is fixed in scilab-branch-6.0:
Huh, what do you mean? Is there a new function bins2d or hist2d in 
scilab-branch-6.0?


Antoine


S.



--
+++

 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] diary lost in try/catch statement .

[amonmayr]

Hello,

As a workaround, if you replace
    1!=0  // syntax error
with
    str="1!=0";
    evstr(str);
it seems to work as you expected.

Anyway, I think the try/catch structure can catch errors occurring at 
runtime (like division by zero, etc ...), but not syntax errors.

You are supposed to write syntactically correct Scilab!

Antoine


Le 03/09/2018 à 11:48, philippe a écrit :

Hi,

In scilab-5 I used to save console output of script file execution in a
text file with "diary", this seems to fail in scilab-6, for new errors
types recently added (Syntax error, Unexpected token ).  Perhaps I
misunderstood something in try/catch statement , let's consider the file
bug_syntax_error.sce containing :

diary(0)
diary('file.txt','new');
try disp('let''s make an error')
 1!=0  // syntax error
catch
 disp('added to diary')
end
diary('file.txt','close')


execute this script with CTRL+SHIFT+E  or "exec" will not create file.txt


--> exec('bug_syntax_error.sce', -1)
à la ligne 4 du fichier exécuté bug_syntax_error.sce

 1!=0  // syntax error
  ^^
Erreur : Unexpected token '!'

--> mgetl file.txt

mgetl : Impossible d'ouvrir le fichier file.txt.

execute this script from scinotes with CTRL+E will give :


--> diary(0)

--> diary('file.txt','new');

--> try disp('let''s make an error')
   > 1!=0  // syntax error
   > catch
   > disp('added to diary')
   > end
 1!=0  // syntax error
  ^^
Erreur : Unexpected token '!'

--> diary('file.txt','close')

--> mgetl file.txt
  ans  =

!  !
!  !
!--> try disp('let''s make an error')  !
!  !
!  > 1!=0  // syntax error !
!  !
!  > catch !
!  !
!  > disp('added to diary')!
!  !
!  > end   !
!  !
!1!=0  // syntax error !
!  !
! ^^   !
!  !
!Erreur : Unexpected token '!' !
!  !
!  !
!  !
!--> diary('file.txt','close') !


I also remark that those new errors (like bad comparisons 1=2  or bad
string delimiters mixing ' and " ) have no localization. This doesn't
happend with "old" errors (which have localization), replacing "1!=0"
with "ieee(0),1/0" I get :

--> exec('bug_syntax_error.sce', -1)

  let's make an error

  added to diary

--> mgetl file.txt
  ans  =

!  !
!  !
! let's make an error  !
!  !
!  !
!  !
! added to diary   !


Best regards,

Philippe

___
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] save and *.sod broken in scilab6 ?

[amonmayr]

Hello Philippe,

(Sorry for the previous email, I send it by accident)

I just tried it under 16.04: no issue, but I confirm the bug under 18.04.
I have exactly the same issue than you.
So it seems related to Ubuntu 18.04.

Antoine

Le 27/08/2018 à 15:31, philippe a écrit :

Le 27/08/2018 à 12:24, Samuel Gougeon a écrit :

Hello Philippe,

No problem for me.
You may have used listvarinfile() at a moment during your trials or work.

no Samuel, the file val.sod doesn't exists in the directory, save don't
create the file due to the error.

Perhaps the bug could depend on operating system ?

Best regards,
Philippe

___
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] save and *.sod broken in scilab6 ?

[amonmayr]

Hello Philippe,

I just tried it at

Le 27/08/2018 à 10:51, philippe a écrit :

Hi,

Running the example of man page for "save" to create an *.sod file
yields an error in scilab-6.0.1 and ubuntu 18.04 (see below) .
It looks like there is no report for this bug on bugzilla ?

Best regards,
Philippe.

-> a=eye(2,2);b=ones(a);

--> save("val.sod", "a", "b");

save : Impossible d'exporter la variable 'a' dans le fichier 'val.sod'.

--> clear a

--> clear b

--> load("val.sod", "a", "b");

load : Impossible d'ouvrir le fichier 'val.sod'.



Version de Scilab : 6.0.1.1518683525
Système d'exploitation : Linux 4.15.0-33-generic
Version Java : 1.8.0_181
Informations sur l'environnement d'exécution Java : OpenJDK Runtime
Environment (build 1.8.0_181-8u181-b13-0ubuntu0.18.04.1-b13)
Informations sur la machine virtuelle Java : OpenJDK 64-Bit Server VM
(build 25.181-b13, mixed mode)
Spécifications du fabricant : Oracle Corporation

___
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] xs2svg and complex grayplot: room for improvements?

[amonmayr]

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] Installing Scilab under Linux (Mint / aka Ubuntu)

[amonmayr]

Hello Claus,

Le 25/07/2018 à 20:01, Claus Futtrup a écrit :

Hi Antoine and Nikolay

Thank you for your help. I see that the easiest way is, as Antoine 
wrote, to execute a shell and execute scilab from the shell (and for 
sure, keep the shell open).
Well, the best solution I found is to use a dropdown terminal (like 
yakuake for example): pressing F12 the terminal appears/disappears. This 
way, I never have to close it and it stays open with a bunch tabs with 
the most common command line applications I use.


I tried to create a desktop "launcher" in Linux Mint, executing a 
scilab.sh script and containing 'nohup scilab.sh & disown' ... to 
release scilab from the terminal, but at no luck.

Well, I think the .desktop approach is the best one here.
You can also try to use a command launcher: with the Ubuntu I use 
(16.04), I have Alt+F2 that opens a proper command launcher and I can 
run any command line app. Note that it differs from pressing the Windows 
key that will only launch applications that have a corresponding 
*.desktop file.


I also tried to follow advice from askubuntu (below), including 
creating desktop files, etc. (see near the bottom), but still no luck.

I don't see your attempt here.
If you installed scilab from the repos, you should have a *.desktop file 
to tinker with in order to call your up-to-date scilab instead of the 
repo one.

On my system the desktop files of the repos applications are here:

    /usr/share/app-install/desktop/scilab:scilab.desktop
    /usr/share/applications/scilab.desktop

while I put the one of the applications I installed by hand  here:

    ~/.local/share/applications/

Hope it helps,

Antoine


Best regards,
Claus

On 25.07.2018 15:40, Nikolay Strelkov wrote:

Dear Claus!

As a temporarily fix you can read this solution on AskUbuntu - 
https://askubuntu.com/a/1029164/66509 
 . I have tested it. Unpacking 
to home folder works as expected (and as before).


Dear Scilab developers!

As long-time Scilab user I can't completely understand how this may 
happen. Please take a look to the mentioned bugs in the linked answer 
above and make real actions to fix these problems. Scilab is 
completely broken in Ubuntu 18.04 LTS (so without real actions it 
will be broken until 2023) and does not work on development version 
18.10 too. Also it does not work on Debian 10. Please contact Debian 
and/or Ubuntu maintainers directly.


Scilab is very often used in educational purposes. For example we use 
it on Ubuntu 16.04 LTS in our university to teach students.
It will be very bad if we lose such a convenient and useful 
software-tool.


---
/With best regards,
Ph.D., //associate professor at MPEI 
,

IEEE member,
maintainer of Mathieu functions toolbox for Scilab 
,

Nikolay Strelkov./

2018-07-25 15:44 GMT+03:00 Claus Futtrup >:


Hi there

I've installed Linux Mint 19 (MATE) and installing Scilab using
the Software Manager doesn't work. I cannot get the GUI to show
up (CLI works fine). There are several bug reports out there, but
AFAIK no remedy. P.S. Upon first installation I did check and see
that the GUI worked, but it never worked since and uninstalling +
installing (incl. the CLI, and BTW also including reboots)
doesn't work.

Therefore I decided to download the Linux 64-bit package from
scilab.org  ... when unpacked, I see there's
not an installer ... but as the README says, launching
./bin/scilab gives me the GUI (yaayh!)

The question is - from unpacking the software, how am I supposed
to install this already compiled scilab in my Linux? ... Am I
supposed to leave it in my /home directory? ... Sorry for my lack
of knowledge here. I hope for some kind help.

Best regards,

Claus


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus 

___
users mailing list
users@lists.scilab.org 
http://lists.scilab.org/mailman/listinfo/users








Avast logo   

This email has been checked for viruses by Avast antivirus software.
www.avast.com 


<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>


___
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

 

Re: [Scilab-users] Possible bug: export to JPEG

[amonmayr]

Hello Lester,

It might be unrelated, but at some point, there was an issue with 
displayed or exported graphics being pink or reddish.

It was always due to the drivers of the graphic card.
Could you try to upgrade (or downgrade) your drivers?

Hope it helps,

Antoine


Le 11/06/2018 à 09:47, Lester Anderson a écrit :

Hi all,

I am using Scilab 6.0.1 and there seems to be an issue with export to 
JPEG (low or high resolution). See attached low-res image.


Tested this using xs2jpg and export figure from the graphic.

Other export options seem to be fine, PNG has no problem.

Cheers
Lester


___
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] [EXTERNAL] Re: submatrix issue

[amonmayr]

Le 01/06/2018 à 12:46, Carrico, Paul a écrit :


Evstr(resu(k)) is a paste error - I’m reading an asci file J

Without using a loop, I would like to get the n th component of the 
vector resu(k) … k is no more no less than the index of specific lines 
I’m trying to get …


Through your answers I’m understanding that I’m thinking on a bad way



I think you can achieve what you want to do without a for loop.
But my feeling is that there is something wrong with the way you index 
your matrix NodesMatrix2(i,j+1) and your results resu(k).
When you index with "i" and "j+1" that are vectors of length N & M, you 
are basically indexing NxM elements of you matrix.

This seems to be the core of the issue here.
Maybe  indexing your matrix like a vector (ie NodesMatrix2(p) with p in 
[1:length(NodesMatrix2)]) would be better.


Antoine


Paul

*/EXPORT CONTROL :
/**Cet email ne contient pas de données techniques
This email does not contain technical data*

*De :*users [mailto:users-boun...@lists.scilab.org] *De la part de* 
antoine monmayrant

*Envoyé :* vendredi 1 juin 2018 11:55
*À :* users@lists.scilab.org
*Objet :* [EXTERNAL] Re: [Scilab-users] submatrix issue

Hello,

What do you wan to achieve exactly?
As Stéphane pointed out, the sizes are not the same.
When you assign something like:

A=B;

You have two different situations:

1) size(A)==size(B)
2) size(B)=[1,1]

In the first case, you assign each element of B to each element of A. 
In the latter case (which corresponds to your commented line), B is 
just a scalar that gets assigned to each element of A.


In the current situation, you are neither in case 1) nor in case 2).
As you have size(NodesMatrix2(i,j+1))=[300,300] and 
size(resu(k))=[300,1], you might want to replicate resu(k) 300 times 
and fill NodesMatrix2(i,j+1) with these 300 copies. If this what you 
want to do, here is the code:


NodesMatrix2(i,j+1)=resu(k)*ones(1,300);

By the way, why do you use "evstr(resu(k))" instead of "resu(k)"?

Antoine

Le 01/06/2018 à 11:45, Stéphane Mottelet a écrit :

It cannot work since

--> size(k)
 ans  =

   300.   1.


--> length(i)*length(j)
 ans  =

   9.

i.e. NodesMatrix2(i,j+1) has 9 elements and resu(k) has 300

S.

Le 01/06/2018 à 11:07, Carrico, Paul a écrit :


Dear all

I’ve a submatrix issue on the following example, and I do not
remember (or understand) why : how can I do this ?

(the goal is to extract and to store within a matrix results from
an Ascii file)

Thanks for any help

Paul

###

mode(0)

clearall

StartNodeLine= 1;

NumberOfNodes= 100;

DimCoordinates= 3;

resu= rand(1000,1);

tic();

NodesMatrix2= zeros(NumberOfNodes,DimCoordinates+1);

i= [1 : NumberOfNodes]'; NodesMatrix2(i,1) =
_evstr_(resu(StartNodeLine + (DimCoordinates+2)*(i-1)+2));

i= [1 : NumberOfNodes]'.*.ones(1,DimCoordinates)';

j= ones(1,NumberOfNodes)'.*.[1 : DimCoordinates]';

k= StartNodeLine + (DimCoordinates+2)*(i-1)+3+j;

a= _evstr_(resu(k));

NodesMatrix2(i,j+1)= _evstr_(resu(k)); /// does not work/

///NodesMatrix2(i,j+1) = 1; // work(basic assignement)/

Duration2= toc()

*/EXPORT CONTROL :
/**Cet email ne contient pas de données techniques
This email does not contain technical data*



___
users mailing list
users@lists.scilab.org 

https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users









___

users mailing list

users@lists.scilab.org 

http://lists.scilab.org/mailman/listinfo/users





___
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

Re: [Scilab-users] How to close/kill "messagebox"

[amonmayr]

Hello,


Indeed, messagebox() seems to live outside the realm of figures and 
other graphic entities.

It's a bit weird in my opinion.
Maybe a workaround for you would be to emulate what messagebox() is 
doing by using a figure and a bunch of uicontrols and callbacks.
That way you'll be able to treat this emulated version like any othe 
figure and close it using delete(winsid_of_said_figure).


Hope it helps,

Antoine



Le 11/05/2018 à 09:42, Emmanuel Delaleau a écrit :




Hi,


Does it exists a way to close/kill windows created by "messagebox".

"close" or "delete" do not work as messageboxes do not have a handle.

Thanks

Emmanuel

___
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] gcf().anti_aliasing : Confirmation of (un)effect?

[amonmayr]

Hello Samuel,

With your example, I don't see any difference on the various computers I 
have.
I think I used anti_aliasing in the past but I cannot find back a script 
where I used it.
I think I used it on 3D plots (surf?), maybe for the export to graphic 
files but I am not sure.

If I can find something I'll let you know.

Antoine


Le 07/05/2018 à 14:36, Samuel Gougeon a écrit :


Hello,

The gcf().anti_aliasing figure property was implemented many years ago 
(in the early Scilab 5.x versions).


It aims to reduce the "staircase effect" for lines drawn very close to 
vertical or horizontal directions.


Yet, has anyone ever seen an actual effect on graphic rendering, as 
expected and described in the related SEP#16 
 
?

I never did, whatever were the computer and its graphic card i used.
Still now with Scilab 6.0, i don't see any effect.

The staircase effect can easily be seen with the following code:

x = [0 1];
y = (0:0.02:1)';
y = [y y+0.02]';
clf
plot2d(x,y)
f = gcf();
f.anti_aliasing  // should display "off" (by default)

f = scf();
f.anti_aliasing = "8x";
plot2d(x,y)
Then compare both figures.
I get the following, whatever is the .anti_aliasing value.


Does anyone get anything else, closer to the expected "dithered" 
rendering?

Either it will be possible to better document the effect of this property,
as requested in the bug report 6777 
, or to reopen the 
bug 11311  reporting

that it is out of work.

Thanks
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] unable to read a hdf5 file under windows

[amonmayr]

Le 19/03/2018 à 11:35, paul.carr...@free.fr a écrit :


Hi All

I'm still wondering why I cannot open a hdf5 file under windows, while 
it works find under linux


(I'm using the latest scilab release in both cases - hdf5 file was 
made using h5py librarie)


The path & file name are corect, so ?

Any trouble under windows?

Paul



PATH  =  get_absolute_file_path("test_read_hdf5.sce");
fichier  =  "Results_gzip.h5";
resu  =  h5open(PATH  +  fichier);

h5open : Impossible d'ajouter des données au fichier (non HDF5) : 
D:\***\Results_gzip.h5.
Description HDF5: unable to open file: name = 
'D:\***\Results_gzip.h5', errno = 2, error message = 'No such file or 
directory', flags = 0, o_flags = 0.




___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users


That's weird.
Can you share a small hdf5 file that exhibits this problem?
I might try to read it from linux/windows.
The only windows-specific hdf5 bug I am aware of is related to unknown 
types for some integers.
Are you sure your problem is not something related to the difference in 
path definition & handling between linux and windows?



Antoine


___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] macOs High Sierra

[amonmayr]

Le 05/02/2018 à 12:44, Philippe Dérogis a écrit :

Hi,

  I upgraded my mac to High Sierra 10.13.3 last week and Scilab 6.0.0 
doesn’t start anymore. I tried to download the nighty build here : 
http://www.scilab.org/en/development/nightly_builds/branch60 and I get 
the 404 error : The requested URL 
/download/2017-08-02/scilab-branch-6.0-1500821730-x86_64.dmg was not 
found on this server.

I would like to know if there is a fix to this situation.

Hello,

It's the same with the master branch: 
http://downloadarea.scilab.org/download/2017-08-02/scilab-master-1501146348-x86_64.dmg 
gives a 404. That's the same for the windows link: 
http://downloadarea.scilab.org/download/2017-07-28/scilab-master-1501146348_x64.exe


Antoine


Any help would be greatly appreciated.

Thanks to all developers and contributors.

Philippe DEROGIS.


___
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] GUI programming

[amonmayr]

Hello,

Last time I built GUI with Scilab, I did not find a comprehensive 
website or book on the subject and resorted to a bunch of separate 
sources (see Nikokay's answer).

Here are a bunch of issues/tricks I learned by trial & error:

- as for now, you cannot export uicontrols using the figure menu or the 
"xs2svg, xs2png, ..." functions. It means that for example if you put 
two frames side by side, one with buttons, the other one with a plot (an 
axis), you'll get a blank image if you export it. It's quite 
inconvenient when trying to build a documentation with visual examples.


- the documentation for gridbag layout constraint is just useless ( 
https://help.scilab.org/docs/6.0.0/en_US/gridbag_constraints_properties.html 
), but this layout is just the best in term of functionalities and 
flexibility. It took me a lot of time to half understand how it works, 
reading java documentations and trying to fill-in the gaps.


- There is a nice trick to get a responsive GUI even if your callback 
functions take some time to execute. The idea is, from within the 
callback function, to first disable the callback function of the 
uicontrol, run the long calculation and then re-enable the callback. 
That way you avoid getting a huge amount of events and callbacks that 
accumulate and lag behind the actions of the user. As an example, 
imagine a slider where the callback function runs a 500ms-long 
calculation and plot the results on a graph. If you don't apply the 
trick described above, sliding the slider can generate 10's of events in 
a fraction of a second and then you have to wait for all the 
calculations and plotting to finish in order to get back to a usable GUI.


Hope it helps,

Antoine

Le 24/01/2018 à 19:49, Claus Futtrup a écrit :

Hi Scilabers

Is there a comprehensive manual or book (in English, or alt German) 
about programming GUI in Scilab? (or a comprehensive web-page)


I've found the Openeering one (18 pages):
http://www.openeering.com/sites/default/files/LHY_Tutorial_Gui.pdf
... and I've looked at the help pages for uicontrol + run some of the 
GUI demos in Scilab.


I have almost no background in GUI programming, nothing successful 
anyway, but it could be nice if I could at least get some basic GUI up 
running (e.g. a figure where one can manage some controls on the left 
side + see the polar plot etc on the right side).


I think that what I need is not just examples. I need explanations, 
and preferably something coherent that I can combine and work with, 
into something that works.


I've installed GUI builder from ATOMS. In the past I've never been 
happy with programming on a high level. I prefer to understand what 
goes on under the hood... so GUI builder is a bit of a desperate grasp 
on my part.


Best regards,
Claus


___
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] ?==?utf-8?q? Both scilab 5.5.2 & 6.0 stopped working (java issue under linux)

[amonmayr]

Le 21/01/2018 à 21:34, Tim Wescott a écrit :

Yes, but how can I have a clue as to what to set them _to_?

Here is what worked for me (no idea why):

#!/bin/bash
export MESA_GL_VERSION_OVERRIDE=3.0 ; scilab $*

Cheers,

Antoine



On Mon, 2017-12-04 at 16:05 +, Clément David wrote:

Hi all,

Nice catch Antoine ! From my understanding of the crash and depending
on your graphic card, you
could switch the actual GL implementation to a well supported one
rather than relying on the latest
GL. For example, using mesa on my Intel i965 system, I can tweak the
used Profile through
MESA_GL_VERSION_OVERRIDE and MESA_EXTENSION_OVERRIDE [https://www.mes
a3d.org/envvars.html].

Regards,

--
Clément

Le lundi 04 décembre 2017 à 16:38 +0100, Antoine Monmayrant a écrit :

Hi all,

Answering my own post: it was a graphic driver issue, as usual.
I switch to another driver and now scilab starts, but all the
graphics windows are empty!

Antoine
  
  
On Monday, December 04, 2017 16:12 CET, "Antoine Monmayrant" 
a...@laas.fr> wrote:
  

Hi everyone,

It seems that some automatic update have broken scilab on my
linux station (16.04.3 64bits).
Any java related feature is broken and only scilab-cli is
working.
As any of you any idea on how to investigate this issue?

Thanks in advance,

Antoine

PS: Here is the crash log:


$ scilab
Could not create a Scilab main class. Error:
Exception in thread "main" java.lang.InternalError: XXX0
profile[1]: GL3bc -> profileImpl GL4bc
!!! not mapped
 at
com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071
)
 at
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfi
le.java:1954)
 at
com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:
1875)
 at
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfi
le.java:1842)
 at
com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
 at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
 at java.security.AccessController.doPrivileged(Native
Method)
 at
com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
 at
com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
 at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
 at
com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
 at
com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
 at org.scilab.modules.gui.SwingView.(Unknown
Source)
 at
org.scilab.modules.gui.SwingView.registerSwingView(Unknown
Source)
 at org.scilab.modules.core.Scilab.(Unknown Source)

Scilab cannot create Scilab Java Main-Class (we have not been
able to find the main Scilab
class. Check if the Scilab and thirdparty packages are
available).

___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users


___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

___
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] ?==?utf-8?q? Both scilab 5.5.2 & 6.0 stopped working (java issue under linux)

[amonmayr]

Le 21/01/2018 à 21:31, Tim Wescott a écrit :

There's a known bug, at least in Ubuntu's bug base.

OK, do you have the link to the Ubuntu bug page?
It's maybe still a good idea to open a scilab bug report, pointing at 
the Ubuntu bug page and listing the workaround, no?


Antoine

It appears to vary by hardware -- it doesn't work on this machine, but
it works on at least one of my laptops.

On Sat, 2018-01-20 at 08:45 +0100, antoine monmayrant wrote:

I just noticed that I did not fill a bug report for that.
I have 3 of my colleagues running Scilab on Ubuntu 17.04 /17.10 that
are
also affected.
Should I fill a bug report or it corresponds to a known one?


Antoine


Le 04/12/2017 à 17:05, Clément David a écrit :

Hi all,

Nice catch Antoine ! From my understanding of the crash and
depending on your graphic card, you
could switch the actual GL implementation to a well supported one
rather than relying on the latest
GL. For example, using mesa on my Intel i965 system, I can tweak
the used Profile through
MESA_GL_VERSION_OVERRIDE and MESA_EXTENSION_OVERRIDE [https://www.m
esa3d.org/envvars.html].

Regards,

--
Clément

Le lundi 04 décembre 2017 à 16:38 +0100, Antoine Monmayrant a écrit
:

Hi all,

Answering my own post: it was a graphic driver issue, as usual.
I switch to another driver and now scilab starts, but all the
graphics windows are empty!

Antoine
   
   
On Monday, December 04, 2017 16:12 CET, "Antoine Monmayrant" 
nm...@laas.fr> wrote:
   

Hi everyone,

It seems that some automatic update have broken scilab on my
linux station (16.04.3 64bits).
Any java related feature is broken and only scilab-cli is
working.
As any of you any idea on how to investigate this issue?

Thanks in advance,

Antoine

PS: Here is the crash log:


$ scilab
Could not create a Scilab main class. Error:
Exception in thread "main" java.lang.InternalError: XXX0
profile[1]: GL3bc -> profileImpl GL4bc
!!! not mapped
  at
com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:20
71)
  at
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLPro
file.java:1954)
  at
com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.jav
a:1875)
  at
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLPro
file.java:1842)
  at
com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
  at
com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
  at java.security.AccessController.doPrivileged(Native
Method)
  at
com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
  at
com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
  at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
  at
com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
  at
com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
  at org.scilab.modules.gui.SwingView.(Unknown
Source)
  at
org.scilab.modules.gui.SwingView.registerSwingView(Unknown
Source)
  at org.scilab.modules.core.Scilab.(Unknown
Source)

Scilab cannot create Scilab Java Main-Class (we have not been
able to find the main Scilab
class. Check if the Scilab and thirdparty packages are
available).

___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users


___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users


___
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] frame, plot & non working zoom: your help for a bug report and a possible workaround

[amonmayr]

Bug submitted: https://bugzilla.scilab.org/show_bug.cgi?id=15325

Thanks for your feedbacks.

Antoine



Le 10/11/2017 à 21:32, Antoine Monmayrant a écrit :

Hello Scilab users,

I'm facing a bug that prevents zooming on a plot inside a frame (or a tab).
Here is my minimum working (or bugging) example:

//
// Two axes in one figure:
// left one is inside a frame
// right one is directly attached to the figure
// GUI zoom and zoom_rect don't work on the left plot

h=scf();
h.axes_size=[800,600];
a_right=newaxes(h);
a_right.axes_bounds(3)=0.5;
a_right.axes_bounds(1)=0.5
plot2d()
a_right.title.text="GUI zoom & zoom_rect work here";

frame_left = uicontrol(h, ...
"style", "frame", ...
"backgroundcolor", [1 0 1], ...
"Position", [0,0,400,600]);
a_left=newaxes(frame_left);
plot2d();
a_left.title.text="GUI zoom & zoom_rect DO NOT work here";
//

Now come the questions:

1) Did you face the same bug and do you know any workaround to zoom on a plot 
inside a frame?
2) I plan to report a bug, any advice on the short summary keywords? "zoom not 
working on plots inside frame or tab uicontrols"?

Cheers,

Antoine

___
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] How to read in date & time ?

[amonmayr]

Hello Richard,

There are:

datevec
datenum
getdate

that could do the job.
I am not sure whether there is a recommended way of doing the conversion.

Cheers,

Antoine



Le 07/11/2017 à 15:38, Richard llom a écrit :

Hello,
I have logfiles in the following form:
DESC: AAA 2017
Datum;Zeit;kWh
01.01.2017;06:00;419,942
01.01.2017;07:00;513,273
01.01.2017;08:00;478,268
01.01.2017;09:00;711,572
01.01.2017;10:00;606,592
01.01.2017;11:00;594,92
01.01.2017;12:00;594,92
01.01.2017;13:00;524,933
...

I can read these in either as double or string
[log_data, comments] = csvRead(log_file, ";", ",", "double",[],
"/^[^0-9\-]/");

[log_data, comments] = csvRead(log_file, ";", ",", "string",[],
"/^[^0-9\-]/");

However what I'm missing is a way to convert the date & time column to a
date format in scilab. There doesn't seem to be function for this in scilab.
Is there a recommended way of doing so?

Thanks & regards
richard


PS:
I'm so glad the list is working again! Would have been nice tho to inform
the users in advance and with some sort of status.scilab.org site or
something...



--
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



--
+++

 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] GUI Builder 4.0.1 for Scilab 6.0

[amonmayr]

Dear Frieder,

In Scilab 6.0 a breaking change was introduced: adding an empty matrix 
to a constant now gives an empty matrix, not a constant.
This causes a lot of issues with existing codes that relied on the old 
behaviour.
Apparently, this is the case for GUI Builder that was not properly 
refactored for Scilab 6.0.

I think you should report this to the maintainer of the module.

Hope it helps,

Antoine


Le 04/05/2017 à 09:13, Frieder Nikolaisen a écrit :


Dear Community,

I am using the GUI Builder again (last time Oktobre 2016), now with 
Scilab 6.0.0.


I started to Design the interface, generated the GUI. Had the GUI run 
and wanted to reload it. But:



--> guibuilder
operation -: Warning adding a matrix with the empty matrix will give 
an empty matrix result.
operation +: Warning adding a matrix with the empty matrix will give 
an empty matrix result.

at line60 of function guigetfile
at line 4 of function openfile
at line 9 of function open_existing_gui

':': Wrong type for argument 1: Real scalar expected.

And with the old version I am used to (but its still desigend with 
Scilab 6):


START GUI Builder 3.0 for Scilab 5.5
Load macros
Load help
Type "guibuilder" to start the GUI


-->guibuilder
  !--error 21
ungültiger Index.
at line   8 of function openfile called by :
at line   9 of function open_existing_gui called by :
= gcbo; end;gcbo = 
getcallbackobject(118);open_existing_gui(handles);if 
exists("%oldgcbo") then gcbo = %oldgcbo; else clear gcbo; end

while executing a callback

The file is attached.

Scilab 5.5 and 6 open the programm with save and run. But not with the 
Builder.


*Whats wrong?*

Best regards

Frieder



___
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] Exporting figures containing uicontrols to any format

[amonmayr]

Hi all,

Just in case it can help someone else, here is the code I hacked this 
morning to get a proper export menu on my figures.
It really is a hack and should probably work only on my machine (linux 
64 bits, X window, ImageMagick) and with my current figure layout:


//

   // New menu
   h = uimenu(demo_fp, ...
   "label" , gettext("File"));

   // Export entry
  uimenu(h, ...
   "label" , gettext("Export Figure (Hack)"), ...
   "callback"  , "exportHack();", ...
   "tag"   , "export_menu");


function exportHack()
   // Export figure with uicontrols to png using X server & import 
(imagemagick)

   // Horrible hack the should only work on my machine (linux 64bits.
   // get around bug http://bugzilla.scilab.org/show_bug.cgi?id=14836 
https://bugzilla.scilab.org/show_bug.cgi?id=14502

h=gcbo;
//current figure name
figname=h.parent.parent.figure_name;
//getting X server id for current window
ret=unix_g("xwininfo -int -name " ++figname+);
//hackish, depends directly on the syntax of xwininfo outputs
tok=tokens(ret(2),':');
   tok=tokens(tok(3)," ")
   winid=tok(1);//X server windows id, as a string

   // File save dialog parameters
   file_mask=["*.png"];
   boxTitle="Export";
   //If previous filename is present, use it to start the dialog in the 
corresponding directory

   if h.userdata~="" then
  dir=h.userdata;
   else
  dir=pwd();
   end
   dir
   PathFileName=uiputfile(file_mask,dir,boxTitle);
   // LD_LIBRARY_PATH required to get around bug: 
http://bugzilla.scilab.org/show_bug.cgi?id=14143
unix_s("LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/:$LD_LIBRARY_PATH ; 
import -window "+winid +" "+PathFileName)

  //   keep savec filename for future reference.
   h.userdata=PathFileName;
endfunction

//


Hope it helps,

Antoine

Le 04/11/2016 à 23:46, Philipp Mühlmann a écrit :

pittywise   driver()   does also not brings the solution

interstingly playing with usecanvas()  made it possible to only show 
pushbuttons in a figure.


e.g.:
usecanvas(%T);
f=figure();
plot2d();
h=uicontrol(f,'unit','normalized',"style","pushbutton","string","pushbutton",  
'Position',[0.1,  0.7,  0.2,  0.1]);
h=uicontrol(f,'unit','normalized',"style","frame","string","frame",  
'Position',[0.1,  0.5,  0.2,  0.1]);

but expoting this figure as a image file resulted in having the know 
style.
no pushbuttons rendered, only the figure of plot2d().(also not the 
frame)





2016-11-04 1:50 GMT+01:00 Philipp Mühlmann >:


it seems that:

exportUI() only recognizes figure handles (and axes) for the export.

since pushbuttons etc. are not figure handles they are not exported?


e.g.: handles.mypushbotton.style = "pushbutton"

...should be maybe "figure", "frame" or "axes" to be recognized by
exportUI().

Seems to be the same with "printfigure()"




sidequestion:

Is it possible to export content of a xml-file to an figure/image?

If so one could maybe use:

saveGui(gcf(),  'screenshot.xml');

and than convert the content of the xml file into an image?









2016-11-03 23:08 GMT+01:00 Philipp Mühlmann >:

Dear all,

searching a little how GUI's can be "screenshotted" in Matlab
gave me following:

Request on a Matlab forum, see:

https://de.mathworks.com/matlabcentral/newsreader/view_thread/146264


[...] " In order to show users without atlab on their desktop
the output, i want to create a export function."

This could be the reason for having the oppertunity of
screenshotting a GUI.

Anyways:

to me it seems that following is needed to do the trick:

[name,path,index] = uiputfile
saveas(guifigurehandle,[path name]);

while   "saveas" calls  "print"
see "ocatave" code:
https://fossies.org/dox/octave-4.0.3/saveas_8m_source.html


The print.m code is than way beyond my code understanding.
see "ocatave" code:
https://fossies.org/dox/octave-4.0.3/print_8m_source.html



best regards,
Phil






2016-11-02 23:07 GMT+01:00 Rafael Guerra
>:

Hi Antoine,

I do not have an answer but a question, if you will.
Why is it important for you to export the whole shebang
from Scilab?

For the regular figures the export functions work fine and
generate high-resolution post-script files.
 

Re: [Scilab-users] Spinner control with non-linear step?

[amonmayr]

Le 03/31/2016 12:58 PM, scilab.20.browse...@xoxy.net a écrit :

Onward and upward thanks to Antoine.

I'd like to have a spinner uicontrol where the steps are non-linear.

Eg. logarithmic: -10^3, -10^2, -10^1, -10^0 -10^-1, -10-2, -10^-3, 0, 10^-3, 
10^-2, 10^-1, 10^0, 10^1, 10^2, 10^3


Well, you can always use the "linear" values of the spinner as the input 
of a function to generate your non-linear function.

For example something like:
SpinnerValue=hspinner.value;
NLValue=10^Spinnervalue;

To get an exponential scale out of the Spinner value.

Is this something like that you want to achieve?

Antoine



Is it possible to supply a function or vector for the SliderStep property?

Any suggestions for a way to achieve teh goal?

Thanks Buk.


Can't remember your password? Do you need a strong and secure password?
Use Password manager! It stores your passwords & protects your account.
Check it out at http://mysecurelogon.com/manager



___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users



___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] leastsq question : what is 'gopt' useful for?

[amonmayr]

Le 03/22/2016 09:54 PM, Samuel Gougeon a écrit :

Hi,

Le 22/03/2016 10:55, Stéphane Mottelet a écrit :

Hello,

Le 22/03/2016 10:41, antoine.monmayr...@laas.fr a écrit :

Hi everyone,

I have a very general and naive question concerning leastsq: what am 
I to do with "gopt", the "gradient of f at xopt"?


Is there a way to link it to the confidence interval for each 
parameter of my fit?
Not really, but since leastsq is a wrapper for optim, which returns 
the gradient at returned "optimal" solution, it is also returned. 
However, if the final gradient is seen to be far from the zero 
vector, then all confidence intervals based on the inverse of the 
Fisher matrix (computed with the Jacobian) will not have any sense, 
since these "linear" statistics are based on a development where the 
first term (using the gradient) is supposed to vanish... Hence, 
having access to the final gradient can be of interest.


We may guess that, if bounds constraints are set for x, a non-zero 
gradient could as well be returned whether xopt reaches a point on the 
boundary, where fun() has not a true minimum, just a negative 
interrupted slope leading it to a low value.


Right.
I usually check whether a given parameter is equal to one of its 
boundaries to avoid this kind of issues.


For the moment, I know how to estimate these confidence intervals 
when I have access to the Jacobian matrix of my fit function.

I am not sure that we are speaking about the same jacobian.
Well, I am talking about the dfun() function as described in the help 
page of leastsq.
I use it to get an estimate of the confidence interval for each 
parameter of my fit based on "Least Squares Estimation", SARA A. VAN DE GEER
Volume 2, pp. 1041-1045,  in Encyclopedia of Statistics in Behavioral 
Science, ISBN-13: 978-0-470-86080-9.
On one hand, we have some c(i) coordinates (say of spaces: c(1)=x, 
c(2)=y, etc))
on which fun() depends. On the other hand, we have p(j) parameters on 
which fun() also depends.
As good quiet parameters, p(j) have fixed values, whereas c(i) are 
varied by leastsq().


Well, I am not sure I follow you here.
I usually describe my fit functions as yfit=myfit(x,param) and try to 
find the best param to fit some experimental measurements {yexp,xexp}, 
ie such that |yexp-myfit(xexp,param)| is minimized (in the least square 
sense).

Are my xexp your p(j) and my param your c(i)?



AFAIU, Stephane's answer assumes that the x "passed" to leastqr() is 
the full set gathering {c(i)} AND {p(j)}.
Whereas, still afaiu, you look interested in somewhat getting the 
sensitivity of fun() with respect to each
parameter p(j) around the minimum value of fun({c(i)}) (parameters 
p(i) being fixed in the fun()

definition).

Nope, I don't think.
I just want, in my case, to see how much I can vary each param(i) 
without really altering the minimization of yfit-yexp.
The idea is to get grasp of how sharp is the minimization with respect 
to each param(i), in order to determine how to interpret and later use 
the param(i) given by the fit. (if param(1)=12.235658+/-1.0, it does not 
make sense to look too closely at the decimal part).


This can be achieved using Jackknifing or Bootstrapping (see for example 
http://www.jstor.org/stable/2289075?seq=1#page_scan_tab_contents), but 
these methods are resource intensive.

Using dfun() and some assumptions give a way faster estimate.
Here, i don't think that we can speak more than about sensitivity. 
"Confidence" is not the proper term,
since parameters values p(j) are deterministic and fixed. They are not 
random variables.
To assess this sensitivity, you will need the fun() jacobian, BUT with 
respect to p(j), not wrt to c(i) !


To get what you want, i could suggest to run leastsq() with x={c(i)} U 
{p(j)}
Then, unless the optimum is reached on a boundary, the absolute value 
of the derivative of order
*2* of fun() along each p(j) direction evaluated at xopt will be 
related to the "confidence interval",
Unless the derivative of order 2 vanishes as well... (so then of order 
3... etc)
Well, that is how I understood the calculation of the confidence 
interval as described in "Least Squares Estimation".
The scaling factor depends on the kind of interval of confidence you 
choose (90,95,99%, ...).
A more pragmatic way to get this interval could be to evaluate fun() 
around xopt, just varying
(with grand()) the p(j) component of xopt you want to get the 
confidence, and measuring the

spread of fun()'s answers.

Well, I am not sure to see how to use what you propose in practice.
In particular, how do I measure the width of the spread around the 
optimum value?
It's easier with jackkniffing where this width is the sigma of the 
distribution of param(i) across the various fits.


Could "gopt" be of some use to estimate the confidence intervals 
when the Jacobian matrix is not known?

As Stephane said, in no way.

Yep, I was totally wrong there...

Thanks,

Antoine


HTH
Samuel

Re: [Scilab-users] plot bug in scilab 6.0 beta1

[amonmayr]

Answering my own post: I just restarted scilab and can no longer 
reproduce this bug, weird...


Antoine



Hi all,

I found a bug in scilab 6.0 beta1.
Plot seems to fail for some curves when trying to specify a color 
different than the default one:


//BUG PLOT:

i=[-100:100];
i0=10;
di=4.0.^((i/i0)^2);

//OK, no error
scf();
plot(i,di);

// Error: Invalid index
scf();
plot(i,di,'r');

in builtingetLineSpec ( 
/home/myhome/softs/scilab-6.0.0-beta-1/share/scilab/modules/graphics/macros/getLineSpec.sci 
line 11 )
at line   336 of function plot( 
/home/myhome/softs/scilab-6.0.0-beta-1/share/scilab/modules/graphics/macros/plot.sci 
line 348 )


Invalid index.

I don't know exactly how to phrase my bug report to state the problem 
clearly.

Any idea what's wrong and how to say it properly?



Antoine
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users




___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] How to replicate what "load" does (aka creating variable in the current workspace from inside a function)

[amonmayr]

Le 02/23/2016 10:25 AM, antoine.el...@scilab-enterprises.com a écrit :

Hi users,

Just to explain, why "who" change.
Previous implementation of "who" was stack dependant, so when you ask 
local variables names,
Scilab 5 reads the stack from bottom to top ( or the opposite ), and 
returns list of variables it found.


Now in Scilab 6, we have remove this stack ( i'm sure you already know 
that ^^ ).

And we use map to store local variables names.
maps are pretty fast but do not ensure order of elements.
"who" returns a list of local variables names, that's all.

The alphabetical order is a side effect of implementation like 
creation order was in Scilab 5.
If we use another system to store local variables names, we can get 
another output.


So please, do not use "alphabetical" order without "sorted" argument. 
It may change in future.


OK, thanks for the in-depth explanations.
Any chance to get some sort of time-stamp or order info with 'who' or 
any other function?
Because that was a neat feature to know right away what were the last 
variables created.





Antoine
ps: I'm pretty sure that "who"'s help page does not say "'who' returns 
variables names in creation order."

Indeed, it does not.
But now we have an option to sort them whereas they are already sorted. 
Kind of weird and confusing.


Le 2016-02-22 12:51, Antoine Monmayrant a écrit :

Not sure if it is related to `who` or to the special use of `resume`.


I can confirm that it comes from the bug in who for scilab 6.0.
See also my solution that uses 'resume' and not 'who' and work in both
5.5 and 6.0

Cheers,

Antoine


___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

___
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] disp(a,b,c) => display a, b, and finally c ; not c, b and then a <= Re: News: Scilab 6 Beta, VISA Toolbox, Embedded World 2016

[amonmayr]

Le 02/17/2016 02:55 PM, Samuel Gougeon a écrit :

Hello Scilab Team,

The impact of the changed []+a is pointed in this thread.

Since an extensive code review will be needed from Scilab 5 to Scilab 
6, some other long standing bugs could be fixed before the final release.

Already,

  * The 1./m trick is fixed (now parsed as 1 ./m rather than 1. / m)):
Great!
  * The space between the minus sign and the absolute mantissa is
removed when numbers are displayed in the console: Great!
Copying/pasting will now be straightforward.
  * ...

But still, for instance, the unconsistent display by disp() inversed 
wrt to the order of its parameters is still there. Wouldn't it be the 
best moment to correct it as well?
http://bugzilla.scilab.org/5512 http://bugzilla.scilab.org/9463 
http://bugzilla.scilab.org/13447


What about adding to the list the infamous forgotten ";" after a huge 
matrix, aka "huge matrix display scrolling of death"?
See 
http://mailinglists.scilab.org/Scilab-users-Accidentally-displaying-huge-matrices-tc4032315.html#a4032319 
and http://bugzilla.scilab.org/show_bug.cgi?id=6286

It seems that a patch was proposed but never merged?

I have plenty of time to write this email because my scilab session is 
currently trying to list every value in my 2775x570 matrix.

I am not kidding, I did it again, forgot the ";" after a huge matrix, arggh!

Antoine
PS:ah, the last value in my matrix just showed up, back to work!




The impact of this correction on existing codes would be much less 
than for []+a, but would fix a ridiculous behavior met by every user 
(not ones of a highly specific Scilab function or feature).


Best regards
Samuel Gougeon


Le 15/02/2016 16:35, Yann DEBRAY a écrit :


Hello Scilab user,

It has been a while since we last shared news with you. Here are some 
recent updates we hope you will like.



Scilab 6 Beta

Scilab 6.0 is a major new release of Scilab, the open source modeling 
& simulation platform. This beta version is a preview for all users, 
commercial as well as community.


*What's new: *

--> New computation coreenabling bigger data sets
--> Improved Xcos allowing larger models
--> Utilities for development productivity (debugger, profiler and 
coverage)


To provide relevant informations to the user, we also introduced a 
new view called "Newsfeed".
The release will come soon, so feel free to give us feedback about 
your experience.


Find out more 


Signal acquisition and instrument control
with the Scilab VISA Toolbox (beta version)


In partnership with National Instruments, we have developed a
Scilab interface for measurement devices from leading
manufacturers (National Instruments, Agilent/HP, ... )

Here is the first version of this VISA toolbox for signal acquisition 
and instrument control. This is a beta version: your feedbacks are 
welcome.


TheVirtual Instrument Software Architecture 
(VISA) is a standard for configuring, 
programming, and troubleshooting instrumentation systems comprising 
GPIB, VXI, PXI, Serial, Ethernet, and/or USB interfaces. VISA 
provides the programming interface between the hardware and 
development environments.


Find out more 


Event Embedded World // 23-25 February 2016, Nuremberg

Starting with the largest embedded systems' event of the 
year:Embedded World 2016 

23 - 25 February 2016 in Nuremberg, Germany

We will be present on the booth of Evidence (Hall 4 / 4-545 
_)_ and 
Emmtrix (Hall 4A, booth 520d 
_)_


Scilab has many applications in the field of embedded systems :
--> post-processing of test data
--> automation of tasks
-->prototyping of control algorithms
-->identification of systems parameter
-->simulation of control systems
--> embedded code generation

Here are some use cases of Scilab in this field, from our last 
ScilabTEC :




  * ZYNQ-7000 High Performance Electric Drive and Silicon Carbide
Multilevel inverter with Scilab Hardware-in-the-loop


  * E4Coder on Scilab: State Machines simulation and GUI prototyping


  * Can programming of multi-core systems be easier, please?

Re: [Scilab-users] What is the future of Scilab?

[amonmayr]

Le 02/17/2016 01:23 AM, AlvaroOsvaldo a écrit :
I am worried, in previous versions of scilab, I implemented a medium 
project for scientific computing with scilab at that time had many 
memory leaks and had been a nightmare. With the new updates that was 
fixed and this much better.  But now I am implementing another project 
involving massive image processing. And the three atoms for this, one 
does not work, one does not load images but the manual says they can 
do, and other charges but leak the computer's memory and it took me 
longer skirting the problem than implementing the solution. And worse, 
because this the system is much slower than it should. This atom 
memory failure it has been known, however, despite it make 
impraticable to use the atom for medium and large projects, makes 
three years that no one gets the bug. 
forge.scilab.org/index.php/p/IPD/issues/992/ There are high 
expectations with Scilab 6 and I believe we will have a much better 
platform. But for what you know, in the meantime we will run out of 
many atoms, and this greatly reduces the possibility of working in 
scilab. What is the future of Scilab? For now, the impression I have 
is that the atoms are abandoned and without the atoms the usefulness 
of scilab is reduced a lot.


Hi,

I think there are two issues here:

1) The sad state of image processing toolbox with Scilab. It's 
terrrible. Image processing with Scilab is a nightmare. Every other 
language I use is far better than Scilab in this area (even extremely 
young language like Julia offers a better experience. The 3 toolboxes 
are either broken, unmaintained or difficult (or impossible) to install. 
And the experience is even worse under Linux (IPD for example requires a 
very old version of opencv to be manually installed under Linux which is 
a daunting task for most user and which introduces many compatibility 
issues with other softwares relying on opencv).


2) The lack of information on the life (or lack of life) for a given 
atoms module. I know some information is available on the atoms website, 
but I've always found it difficult to determine whether the package was 
long dead or under active development. There are some long dead modules 
that are still listed alongside with actively maintained ones and that 
show excellent rating. It's a bit confusing.


Concerning the first issue, image processing with scilab, I think a 
basic core image support should be part of scilab.


Antoine






View this message in context: What is the future of Scilab? 

Sent from the Scilab users - Mailing Lists Archives mailing list 
archive 
 
at Nabble.com.



___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users



___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] News: Scilab 6 Beta, VISA Toolbox, Embedded World 2016

[amonmayr]

Le 02/16/2016 11:55 AM, Eric Dubois a écrit :


Hello

Thank you for this release and the improvements this Scilab version 
contains.


I have however a major concern with the change of behaviour of the 
addition or subtraction of a null matrix to another matrix. As 
explained in the release notes, []+a will now result in [] whereas it 
resulted in a in previous versions.


This means that developments made under older Scilab versions will 
have to be adapted to Scilab 6.0. This is potentially a huge task, 
since all additions or subtractions in the programs have a priori to 
be checked. Needless to say, additions and subtractions are very 
pervasive operations in numerical programs. And since all additions 
and subtractions cannot be checked in a systematic way (in my toolbox, 
I have more than 20 000 of them!), the needed modifications will be 
made over a long period of time, at the rhythm of the discovery of 
bugs by a developer or its users.


More worrying still, not all additions or subtractions involving null 
matrices will generate errors when switching from Scilab 5 or older to 
Scilab 6: for example, z=size([a+1 y],1) applied to the null matrix a 
will simply add 1 in Scilab 6 to the result of Scilab 5, without 
generating errors. The attentive user will be alerted by the warning 
message generated by Scilab 6, but the inattentive one may not notice 
it or fully understand its consequences. So it may lead some users to 
generate wrong results without being aware of it, which should be very 
embarrassing for the provider of the programs used and for 
Scilab-enterprises itself.


Another problem will come from users sticking to Scilab older 
versions: as for me I have regularly e-mails from users that work for 
a reason or another on old Scilab versions (5.3.3 at the moment for 
instance): avoiding problems to these users will constrain the 
adaptation, prevent from using all capabilities of Scilab and 
complicate the code. With my example, it will be necessary to 
introduce a conditional such as:


if isempty(x) then

   z=size(y,1)+1

else

   z=size([a y],1)

end

And this will apply to new programs as well, which will need so much 
care that, I fear, some cases will be missed by even the most careful 
programmer. And in this case users working with older Scilab versions 
will not even be alerted by a warning message.


Moreover, considering the importance of the change, it is all the more 
surprising that it has not been announced in advance, as was the 
–good– practice for previous changes, even minor (such as the 
replacement of x^n by x .^n when x was a vector, a change that a) 
affected much less numerous lines of code b) did entail a simple 
replacement of some ^ by .^ c) had no side effect).


Don’t other Scilab users share my concern?



Well, I understand your concern.
However, I buy the fact that this change will make the language more 
consistent.
Indeed, "ms=m+s" where m is a matrix and s a scalar gives a matrix ms of 
same size than m in most cases (ie when m is not empty).
It thus makes sense that adding a scalar to an empty matrix returns an 
empty matrix.
This is also the default behavior with other similar languages like 
octave, matlab, julia, so it makes sense.

I think the old behavior was kind of weird.
But you are right that this is a major change that will introduce subtle 
and hard to find bugs.
We should keep in mind that it's a major change (5.x->6.x) and I think 
the last one (4.x->5.x) was even worse in terms of backward compatibility!


Cheers,

Antoine


Regards

Éric.

PS: I find a little bit provocative the sentence in the release notes: 
“To simplify the transition of your code base during beta, a specific 
warning is issued when such operation is detected”. With a little 
exaggeration, it sounds like digging the Great canyon and saying to 
people now separated by it: to help you, we will give you beach 
shovels so that you can build a bridge between the two rivers of the 
canyon...



2016-02-15 16:35 GMT+01:00 Yann DEBRAY 
>:


Hello Scilab user,

It has been a while since we last shared news with you. Here are
some recent updates we hope you will like.


Scilab 6 Beta

Scilab 6.0 is a major new release of Scilab, the open source
modeling & simulation platform. This beta version is a preview for
all users, commercial as well as community.

*What's new: *

--> New computation coreenabling bigger data sets
--> Improved Xcos allowing larger models
--> Utilities for development productivity (debugger, profiler and
coverage)

To provide relevant informations to the user, we also introduced a
new view called "Newsfeed".
The release will come soon, so feel free to give us feedback about
your experience.

Find out more 


Signal acquisition and instrument 

Re: [Scilab-users] Problem installing modules manually (atomsInstall)

[amonmayr]

Le 01/15/2016 01:45 PM, Lester Anderson a écrit :

Hello,

Tried setting the proxy with the settings our IT guy gave in the
Scilab preferences and it still failed, basically thinking it could
not access the Internet (which is incorrect)!

Trying the manual install again (downloaded a toolbox zip file) it
looks like it still needs access!

-->atomsInstall('scinetcdf_1.1.bin.x64.windows.zip')

!
  !
!
  !
!gzip: C:\Users\xxx\AppData\Local\Temp\SCI_TM~1\ATOMS~1\1_TOOLBOXES.gz: not!
!  in gzip format
  !
WARNING: atomsDESCRIPTIONget: Extraction of the DESCRIPTION file
('C:\Users\landerso\AppData\Local\Temp\SCI_TM~1\ATOMS~1\1_TOOLBOXES.gz')
has failed.
Scanning repository http://atoms.scilab.org/5.5 ... Skipped

  !--error 1
All ATOMS repositories scan failed.
at line 198 of function atomsDESCRIPTIONget called by :
at line 227 of function atomsInstall called by :
atomsInstall('scinetcdf_1.1.bin.x64.windows.zip')

and ...

-->atomsInstall('apifun_0.4.2-3.bin.zip')
  !--error 21
Invalid index.
at line 170 of function atomsInstall called by :
atomsInstall('apifun_0.4.2-3.bin.zip')

Confused to say the least the errors vary between the different archives.

I thought that atomsInstall could be used to install a module
downloaded without having access to the Internet.


Well, there is something weird in the way the atoms system is working.
Whenever you install a package, it first fetches the list of all 
available packages (which takes a while).

I just ran a test by
I didn't find a way to turn it off.
It's particularly annoying because it re-fetched everything even if the 
list was updated seconds ago during a previous install.

When you install sequentially 5 local packages, it's really infuriating!
There's room for improvement:

- By default, turn off fetching when installing a local package,
- Cache locally the list and avoid refetching if there is no change or 
if it was updated XX minutes ago.
- Speed-up the process of updating the list: on my computer it takes 3 
minutes!


Antoine






On 15 January 2016 at 10:42, Lavitha Pereira  wrote:

Hi Lester,

If you are under proxy, follow the below instructions.

Configure the network proxy


atomsSetConfig("Verbose","True")
atomsSetConfig("useProxy","True")
atomsSetConfig("proxyHost","myProxyHost")
atomsSetConfig("proxyPort","myProxyPort")
atomsSetConfig("proxyUser","myUserName")
atomsSetConfig("proxyPassword","myPassword")


Read the more documentation below:
https://wiki.scilab.org/ATOMS

Reagrds,

Lavita Pereira



On Fri, Jan 15, 2016 at 3:59 PM, Lester Anderson 
wrote:

I assume that the following error from atomsGui is due to no direct
port access to the Internet? The webpage links from Scilab work fine.

Somewhat at a loss as to how to proceed. Do I need to get the IT guys
to open a port/proxy access ?

Works fine when I do things from home.

Cheers

On 15 January 2016 at 06:37, Lester Anderson 
wrote:

Just installed v5.5.2 and get the same issue when trying to install a
module manually, error 21 at line 170 of atomsInstall

Scilab is installed in Program Files on Windows, and so I am guessing
that it might be a permissions issue for a work machine?

On 13 January 2016 at 08:51, Lester Anderson 
wrote:

Hello,

I currently have v5.4.1 of Scilab, and have to install modules
manually.

I am trying to install apifun (as quite a few modules use it), but get
this error

-->atomsInstall('c:\ss20-work\scilab\apifun_0.4.2-3.bin.zip')
  !--error 21
Invalid index.
at line 170 of function atomsInstall called by :
atomsInstall('c:\ss20-work\scilab\apifun_0.4.2-3.bin.zip')

Checked the code for atomsInstall:

eb_ki.Callback = "updateedit_ki";  Line 170

Any ideas how to resolve this? Will have to follow the same procedure
for v5.5.2 when I update.

Thanks
Lester

___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users




--
Thanks & Regards,
Lavitha M. Pereira

___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users


___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] An Image processing toolbox that *works*

[amonmayr]

Le 01/13/2016 08:34 AM, CHEZE David 227480 a écrit :


Same conclusion for me and also question reagrding scilab 6


Well, I use both scilab 5.5.X and 6.0.X but:

//scilab 6.0.X
--> atomsInstall('IPD')
atomsInstallList: The package IPD is not available

Antoine


David

*De :*users [mailto:users-boun...@lists.scilab.org] *De la part de* 
Philipp Mühlmann

*Envoyé :* mardi 12 janvier 2016 20:11
*À :* Users mailing list for Scilab 
*Objet :* Re: [Scilab-users] An Image processing toolbox that *works*

Hello,

I've been using IPD and SIVP a lot with Scilab 5.5.1 and 5.4.1...on 
WinXP 32 bit and Win7 64 bit.


Both times with IPD 8.3.2-0


IPD would be my favourite.

Anybody uses IPD with Scilab 6?

Best regards,

Philipp



2016-01-12 13:43 GMT+01:00 Samuel Gougeon >:


Hello,

Le 12/01/2016 12:53, antoine.monmayr...@laas.fr
 a écrit :

Hi everyone,

This message is not a rant (but it could).
I am truly looking for an image processing toolbox that works
with current versions of Scilab and a decently modern OS.
I tried every toolbox I've found but without success:

SIVP: requires an outdated version of libtiff that I don't
know how to install on my system.

IPD: does not seem to work properly: ReadImage fails:


Works for me with Scilab 5.5.2 / win7_x64 :

-->dir *.png
 ans  =

foo.png Google_logo.png ico.png scilab.png

-->atomsLoad IPD

Start IPD - Image Processing Design
Load macros
Load dependencies
Load gateways
Load help
Load demos

 ans  =

!IPD  8.3.2-0  allusers  SCI\contrib\IPD\8.3.2-0  !

-->i = ReadImage("Google_logo.png");

-->size(i)
 ans  =

95.275.3.


Do you get an error whatever is the image you try to load?
You may report the error you get @
http://forge.scilab.org/index.php/p/IPD/issues/
 + posting the
image triggering it.

Cheers
Samuel


___
users mailing list
users@lists.scilab.org 
http://lists.scilab.org/mailman/listinfo/users




--

There we have the salad.



___
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] An Image processing toolbox that *works*

[amonmayr]

Le 01/12/2016 08:11 PM, Philipp Mühlmann a écrit :

Hello,

I've been using IPD and SIVP a lot with Scilab 5.5.1 and 5.4.1...on 
WinXP 32 bit and Win7 64 bit.


Both times with IPD 8.3.2-0

IPD would be my favourite.


Anybody uses IPD with Scilab 6?

Best regards,
Philipp


Well, the thing is that it does not work on my computers.
I think this might be due to the fact that IPD expect a specific version 
of OpenCV and does not install it properly (at least on my computer).
I haven't seen simple explanation on how to install (and where to 
install) the right version and I installed the version that correspond 
to my OS.

Why can't we get self-contained image processing tooloboxes under Scilab?
(real question not a rant)
Are the dependencies too difficult to include in the atoms package?

Antoine





2016-01-12 13:43 GMT+01:00 Samuel Gougeon >:


Hello,

Le 12/01/2016 12:53, antoine.monmayr...@laas.fr
 a écrit :

Hi everyone,

This message is not a rant (but it could).
I am truly looking for an image processing toolbox that works
with current versions of Scilab and a decently modern OS.
I tried every toolbox I've found but without success:

SIVP: requires an outdated version of libtiff that I don't
know how to install on my system.

IPD: does not seem to work properly: ReadImage fails:


Works for me with Scilab 5.5.2 / win7_x64 :

-->dir *.png
 ans  =

foo.png Google_logo.png ico.png scilab.png

-->atomsLoad IPD

Start IPD - Image Processing Design
Load macros
Load dependencies
Load gateways
Load help
Load demos

 ans  =

!IPD  8.3.2-0  allusers  SCI\contrib\IPD\8.3.2-0  !

-->i = ReadImage("Google_logo.png");

-->size(i)
 ans  =

95.275.3.


Do you get an error whatever is the image you try to load?
You may report the error you get @
http://forge.scilab.org/index.php/p/IPD/issues/ + posting the
image triggering it.

Cheers
Samuel

___
users mailing list
users@lists.scilab.org 
http://lists.scilab.org/mailman/listinfo/users




--
There we have the salad.


___
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] Atoms fail and changing SCIHOME

[amonmayr]

Le 12/04/2015 10:45 AM, Antoine Monmayrant a écrit :

Le 12/03/2015 07:24 PM, Samuel Gougeon a écrit :

Hello,

Le 03/12/2015 17:10, amonm...@laas.fr a écrit :

Hi all,

We've just discovered that on scilab 5.5.2, atoms is not working on 
our Windows machines:


atomsGUI()
WARNING: mputl: Cannot open file \\servername\username\[..skipping 
some boring stuff...]\scilab-5.5.2\.atoms\config.


It might be a problem with our setup where the homedir of our users 
are on network shares.
Many Windows scripts are failing when accessing the files using the 
network path "\\servername\username\..."
The network shares "\\servername\username" are mapped locally to a 
drive letter "Z:" and usually, changing the path from 
"\\servername\username\..." to "Z:\\..." solves the problem of write 
access.


So here is my question how do I change SCIHOME (to replace 
"\\servername\username\" by "Z:\")?

I tried, predef, looking in scilab.start, ... but without success.

.
For Scilab on Windows, Scilab uses the environment variable (of the 
OS) APPDATA to build SCIHOME, and TMP to build TMPDIR.
The only way to change these Scilab variables is to run Scilab from a 
batch file in which the environment variables are priorly set to what 
you want for Scilab.




Do you have an example of such script?
I daily do things like that under Linux, but I am more than rusty when 
it comes to Windows batch!
Anyway, I am not sure changing APPDATA will solve the problem, but 
it's worth a try.

Answering my own question, here is a solution
1 Create a batch file myscilex.exe in the bin directory
2 Put this inside:
@ECHO OFF
set APPDATA=Z:\Windows\Application Data

start Wscilex.exe
3 Now launch myscilex.exe
4 Now atomsGui() works !

Antoine
(Happy)






Cheers,

Antoine

We daily use such a configuration now for years, with Scilab 
installed on a shared place on our internal network, and it works.


HTH
Samuel







--
+++

 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

[Scilab-users] Atoms fail and changing SCIHOME

[amonmayr]

Hi all,

We've just discovered that on scilab 5.5.2, atoms is not working on our 
Windows machines:


atomsGUI()
WARNING: mputl: Cannot open file \\servername\username\[..skipping some 
boring stuff...]\scilab-5.5.2\.atoms\config.


It might be a problem with our setup where the homedir of our users are 
on network shares.
Many Windows scripts are failing when accessing the files using the 
network path "\\servername\username\..."
The network shares "\\servername\username" are mapped locally to a drive 
letter "Z:" and usually, changing the path from 
"\\servername\username\..." to "Z:\\..." solves the problem of write access.


So here is my question how do I change SCIHOME (to replace 
"\\servername\username\" by "Z:\")?

I tried, predef, looking in scilab.start, ... but without success.

Any hint?

Cheers,

Antoine
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

[Scilab-users] Help with bvodeS & bvode and unusual boundary conditions

[amonmayr]

Hi everyone,

I'm trying to understand how bvodeS works and whether I can use it to 
solve numerically my problem.

A bit of context:
I have a 1D coupled-mode problem, where I model the propagation along 
one direction (let's call it y) of two modes (one in +y-direction and 
one in the -y-direction).

Schematically, it looks like this:

a(0) -->| ODE |-->a(L)
b(0) <--| ODE |<--b(L)

The ODE is of the first order (only a(y), b(y) and a'(y) and b'(y) in 
the ODE, together with non-constant factors).


The thing is that I have scattering-like boundary conditions.
I know the inputs [a(0)=a0;b(L)=bL] and look for the outputs [a(L)=?; 
b(0)=?].
I am of course also interested in  the values of [a(y), b(y)] for all y 
in [0,L], but the puzzling issue are my boundary conditions.
I basically half of my conditions on one side, the other half on the 
other side.

Can I solve such a system using bvodeS?
If I can, how am I supposed to build "zeta" to reflect that my 
conditions only concerns a(0) and b(L)?

Is this doable to get zeta "with holes"?

Thank you in advance for your help,

Antoine
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users