Re: [Scilab-users] int2d

[fujimoto2005]

Hi Samuel

I fixed it as you pointed out and it worked.
There was another mistake. I misunderstood the function len () of another
language as size () and used it.

Was mesh2d internalized? I have not downloaded the Metanet module, but int2d
worked fine.

I have not used the ATOMS yet, but I will try using it little by little.
Are there any guides that wrote the whole picture?

Best regards
test_biv.sce   



--
Sent from: 
http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] int2d

[Samuel Gougeon]

Hello Masahiro,


function  rt=multNormDensFunc(x_V, m_V, cov_M);


I am not sure about the semi-colon... ?


[I2,e]=int2d(X,Y,list(multNormDensFunc,[0,0],[1,0;0,1]),[0.0001,  1,  20*20,  
4000,  0])


The function expects only one parameter after both 2D operands x_V, m_V, 
while the list provides 2 parameters.

So either the function is missing a y_V, or the list has an extra parameter.
I don't know how int2d() manages this.

In practical, int2d() needs mesh2d() to build and feed its X and Y 
arguments.

While mesh2d() is still an external function in the Metanet module,
that is not Scilab 6 - ready: https://atoms.scilab.org/toolboxes/metanet
...
However, mesh_2() from the CGLAB module 
https://atoms.scilab.org/toolboxes/cglab
should also be able to do the job (hoping that the output is int2d() 
compatible).


These tools should be inside Scilab, or int2d() outsite :
http://bugzilla.scilab.org/8284

For int3d(), it is even worse. I am not sure there is any mesh3d() 
available at all anywhere for Scilab.


Samuel

Le 28/02/2018 à 23:17, fujimoto2005 a écrit :

In order to calculate the expected value of a certain two-variable function,
I have created a density function of two-dimensional normal distribution.
I created a code like the attached file to check the correctness of the
function, but it does not work.
Where is the code wrong?

I have been confirmed int2D supports list format for a function call.
Furthermore running the code doesn't show "called multNormDensFunc1".
This means it fails to call "multNormDensFunc" function.
  
Best regards.


test_multNorm.sce




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



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

[Scilab-users] int2d

[fujimoto2005]

In order to calculate the expected value of a certain two-variable function,
I have created a density function of two-dimensional normal distribution.
I created a code like the attached file to check the correctness of the
function, but it does not work.
Where is the code wrong?

I have been confirmed int2D supports list format for a function call.
Furthermore running the code doesn't show "called multNormDensFunc1".
This means it fails to call "multNormDensFunc" function.
 
Best regards.

test_multNorm.sce
  



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

[Scilab-users] hdf5 format and

[paul . carrico]

Hi 

In the following example, I'm digging into the Scilab help pages in
order to understand how I can use hdf5 format; nevertheless I'm still
wondering how I can have access to the sub-structure (sub-groups and
datasets on them) ? 

(I'm thinking in programming recursive search ...) 

Thanks 

Paul 

###

mode(0)

PATH = get_absolute_file_path("test_hdf5.sce");

// the new file is created
a = h5open(PATH + "/tests.h5", "w");

// a basic group is created
group_name = "MyGroup";
h5group(a, group_name);

// sub-groups creation (using a loop)
for i = 1 : 10
s = group_name + "/sub_group" + string(i);
h5group(a,s)
end

// specific groups & sub-groups
h5group(a, "FEM");
h5group(a, "FEM/NODES");
h5group(a, "FEM/ELEMENTS");

// dataset creation using a data matrix
n = 1E3;
i = (1:n)';
A = rand(n,3);
Nodes = zeros(n,4);
Nodes(:,1) = i;
Nodes(:,2:4) = A;
h5write(a,"NODES",Nodes'); // dataset name is NODES here - do not
confuse with the sub-group
h5write(a,"FEM/NODES2",Nodes'); // dataset name is NODE2 in FEM group
h5write(a,"FEM/NODES/new_nodes",Nodes'); // add of a new dataset names
"new_nodes" in the subgroup NODES in FEM

// tests on the contect of the file (see H objects)
// it's expected to find sub-groups and dataset into them
a.root // list of the groups / datasets and so on at the root
a.root.datasets // specifically list of the datasets

a.root.NODES // provides information's of the "NODES" dataset

a("/FEM")
a("/FEM").datasets
a("/FEM/NODES").datasets

//pause h5close(a);___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Clone a function, continued

[Stéphane Mottelet]

Le 28/02/2018 à 18:48, Samuel Gougeon a écrit :

Le 28/02/2018 à 16:30, Stéphane Mottelet a écrit :

Thanks Samuel, the problem is that

save('macros/%axesData_i_h.bin', '%axesData_i_h')

will produce a .sod file with a .bin extension. Both formats cannot 
be used indifferently for compiled macros of a library : in the 
following code (that can be copy/pasted), a library is built, the 
"fun1" function is saved in sod format, then the reference to 
"fun1.bin" is replaced by "fun1.sod" in the lib file :


path=TMPDIR+'/test/';
mkdir(path)
mputl('function y=fun1(x), y=x, end',path+'fun1.sci');
genlib('test',path)
save(path+'fun1.sod','fun1')
doc=xmlRead(path+'lib');
doc.root.children(1).attributes.file='fun1.sod';
disp(xmlDump(doc))
xmlWrite(doc,path+'lib');
clear
lib(TMPDIR+'/test/')

The following output is obtained:

!standalone="no"?> !

! !
! !
! !
!  md5="a50d8a8cda2cd6036306e08e61ffcbeb"/>  !

! !
! !

Emplacement des fichiers des fonctions : /.

fun1

-->

Unfortunately, calling fun1 crashes scilab...


Last trial for today:

  * Define fun1() in fun1.sci.
  * Compile fun1.sci with genlib(): OK => fun1.bin available
  * Create fun2.bin as a hard link to fun1.bin:
host("mklink /H fun2.bin fun1.bin")  // Windows
  * Update (by hand or code, not with genlib) the lib file:


   
   

  * load the library (OK : both fun1 and fun2 are loaded):
--> lib ./
 ans  =
Functions files location : TMPDIR\test.
fun1  fun2

  * fun1(1)   //=> OK
  * fun2(1)    //  => crash

Already tried this one with fun2.bin as a copy of fun1.bin. I noticed 
that under scilab 5.5.2,


 * Define fun1()
 * fun2=fun1
 * save("fun1.bin",fun1)
 * save('fun2.bin',fun2)

gives a fun2.bin different from fun1.bin as the string "fun1" appears in 
fun1.bin and "fun2" appears in fun2.bin


S.




A bad end.
It is likeky vain to go on fighting without Antoine Elias advices and 
comments :)


Samuel



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



--
Stéphane Mottelet
Ingénieur de recherche
EA 4297 Transformations Intégrées de la Matière Renouvelable
Département Génie des Procédés Industriels
Sorbonne Universités - Université de Technologie de Compiègne
CS 60319, 60203 Compiègne cedex
Tel : +33(0)344234688
http://www.utc.fr/~mottelet

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

Re: [Scilab-users] Clone a function, continued

[Samuel Gougeon]

Le 28/02/2018 à 16:30, Stéphane Mottelet a écrit :

Thanks Samuel, the problem is that

save('macros/%axesData_i_h.bin', '%axesData_i_h')

will produce a .sod file with a .bin extension. Both formats cannot be 
used indifferently for compiled macros of a library : in the following 
code (that can be copy/pasted), a library is built, the "fun1" 
function is saved in sod format, then the reference to "fun1.bin" is 
replaced by "fun1.sod" in the lib file :


path=TMPDIR+'/test/';
mkdir(path)
mputl('function y=fun1(x), y=x, end',path+'fun1.sci');
genlib('test',path)
save(path+'fun1.sod','fun1')
doc=xmlRead(path+'lib');
doc.root.children(1).attributes.file='fun1.sod';
disp(xmlDump(doc))
xmlWrite(doc,path+'lib');
clear
lib(TMPDIR+'/test/')

The following output is obtained:

!standalone="no"?> !

! !
! !
! !
!  md5="a50d8a8cda2cd6036306e08e61ffcbeb"/>  !

! !
! !

Emplacement des fichiers des fonctions : /.

fun1

-->

Unfortunately, calling fun1 crashes scilab...


Last trial for today:

 * Define fun1() in fun1.sci.
 * Compile fun1.sci with genlib(): OK => fun1.bin available
 * Create fun2.bin as a hard link to fun1.bin:
   host("mklink /H fun2.bin fun1.bin")  // Windows
 * Update (by hand or code, not with genlib) the lib file:

   
   
  
  
   

 * load the library (OK : both fun1 and fun2 are loaded):
   --> lib ./
 ans  =
   Functions files location : TMPDIR\test.
   fun1  fun2

 * fun1(1)   //=> OK
 * fun2(1)//  => crash

A bad end.
It is likeky vain to go on fighting without Antoine Elias advices and 
comments :)


Samuel

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

Re: [Scilab-users] Clone a function, continued

[Samuel Gougeon]

About

http://mailinglists.scilab.org/Scilab-users-Scilab-and-hdf5-format-small-survey-tp4037711p4037718.html 
:

Le 28/02/2018 à 14:52, Stéphane Mottelet a écrit :

.../...
Doing things like this is not possible any more. It was was also to 
add persistent variables in libraries, with the same mechanism.


External libraries are not persistent 
. 
They are also erased by the so-loved-by-matlabers

clear
instruction...


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

Re: [Scilab-users] Clone a function, continued

[Samuel Gougeon]

Le 28/02/2018 à 17:43, Samuel Gougeon a écrit :

Le 28/02/2018 à 17:21, Samuel Gougeon a écrit :


On my side, with the following lib file:


   
   

it is possible to load the library, but then, first issue, only fun2 
is reported:

--> lib ./
 ans  =
Functions files location : TMPDIR\test.

fun2

And then, also in this case, calling fun2(1) crashes Scilab...


After 
http://mailinglists.scilab.org/Scilab-users-Scilab-and-hdf5-format-small-survey-tp4037711p4037721.html 
:


When on Windows making a *symbolic link*
--> host("mklink test2.sci test1.sci")  // mklink  copy source

and then running genlib (=> no complain), genlib yields the following 
lib file:



   

!
Then, running fun2(1) crashes Scilab (at least this unstability is... 
constant ;)

Let's try making and using a hard link...


If in the file /myfun.sci/ genlib() does not find any function named 
"myfun",

then genlib ignores it and add no entry to the lib file.

Unless bypassing genlib(), this somewhat prevents using soft or hard 
links for the targeted purpose...


Samuel

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

Re: [Scilab-users] Clone a function, continued

[Samuel Gougeon]

Le 28/02/2018 à 17:21, Samuel Gougeon a écrit :


On my side, with the following lib file:


   
   

it is possible to load the library, but then, first issue, only fun2 
is reported:

--> lib ./
 ans  =
Functions files location : TMPDIR\test.

fun2

And then, also in this case, calling fun2(1) crashes Scilab...


After 
http://mailinglists.scilab.org/Scilab-users-Scilab-and-hdf5-format-small-survey-tp4037711p4037721.html 
:


When on Windows making a *symbolic link*
--> host("mklink test2.sci test1.sci")  // mklink  copy source

and then running genlib (=> no complain), genlib yields the following 
lib file:




  


!
Then, running fun2(1) crashes Scilab (at least this unstability is... 
constant ;)

Let's try making and using a hard link...

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

Re: [Scilab-users] Clone a function, continued

[Samuel Gougeon]

Le 28/02/2018 à 16:30, Stéphane Mottelet a écrit :

Thanks Samuel, the problem is that

save('macros/%axesData_i_h.bin', '%axesData_i_h')

will produce a .sod file with a .bin extension. Both formats cannot be 
used indifferently for compiled macros of a library : in the following 
code (that can be copy/pasted), a library is built, the "fun1" 
function is saved in sod format, then the reference to "fun1.bin" is 
replaced by "fun1.sod" in the lib file :


path=TMPDIR+'/test/';
mkdir(path)
mputl('function y=fun1(x), y=x, end',path+'fun1.sci');
genlib('test',path)
save(path+'fun1.sod','fun1')
doc=xmlRead(path+'lib');
doc.root.children(1).attributes.file='fun1.sod';
disp(xmlDump(doc))
xmlWrite(doc,path+'lib');
clear
lib(TMPDIR+'/test/')

The following output is obtained:

!standalone="no"?> !

! !
! !
! !
!  md5="a50d8a8cda2cd6036306e08e61ffcbeb"/>  !

! !
! !

Emplacement des fichiers des fonctions : /.

fun1

-->

Unfortunately, calling fun1 crashes scilab...


On my side, with the following lib file:



  
  


it is possible to load the library, but then, first issue, only fun2 is 
reported:

--> lib ./
 ans  =
Functions files location : TMPDIR\test.

fun2

And then, also in this case, calling fun2(1) crashes Scilab...


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

[Scilab-users] Clone a function, continued

[Stéphane Mottelet]

Thanks Samuel, the problem is that

save('macros/%axesData_i_h.bin', '%axesData_i_h')

will produce a .sod file with a .bin extension. Both formats cannot be 
used indifferently for compiled macros of a library : in the following 
code (that can be copy/pasted), a library is built, the "fun1" function 
is saved in sod format, then the reference to "fun1.bin" is replaced by 
"fun1.sod" in the lib file :


path=TMPDIR+'/test/';
mkdir(path)
mputl('function y=fun1(x), y=x, end',path+'fun1.sci');
genlib('test',path)
save(path+'fun1.sod','fun1')
doc=xmlRead(path+'lib');
doc.root.children(1).attributes.file='fun1.sod';
disp(xmlDump(doc))
xmlWrite(doc,path+'lib');
clear
lib(TMPDIR+'/test/')

The following output is obtained:

!standalone="no"?> !

! !
! !
! !
!  md5="a50d8a8cda2cd6036306e08e61ffcbeb"/>  !

! !
! !

Emplacement des fichiers des fonctions : /.

fun1

-->

Unfortunately, calling fun1 crashes scilab...


S.

Le 28/02/2018 à 15:09, Samuel Gougeon a écrit :

Hello Stéphane,

I would try the following:
After genlibing the set of regular .sci files,
* save the clone with
   save('macros/%axesData_i_h.bin', "%axesData_i_h")
* add a line in the lib file

The MD5 hash is of the content of the .sci file, that here does not 
exist. It is use by genlib to check whether the .sci must be 
recompiled or not. You may try to set any md5 (or the cloned one). As 
long as you don't recompile the lib with genlib -- just loading it 
with load() or lib() --, this should work.


My 2 cents..

Samuel


Le 28/02/2018 à 14:52, Stéphane Mottelet a écrit :

Hello,

With the new library system, it is no longer possible to clone a 
function in a library. This feature is still documented in the help 
page of "lib" but is not working anymore since saving a user-defined 
scilab function uses the sod/hdf5 format. Maybe one can ask why such 
a feature is needed ? Sometimes it can be usefull to have a function 
which is callable by different names but actually does the same 
thing. The different calling names can come from the adaptation for 
different types of data, which can sometimes lead to the same 
treatment, hence to the same function. Instead of writing two 
functions with the same source code but a different calling name, 
cloning the original one was an interesting feature.


I admit that the way it worked under scilab<6.x was not clean at all 
*but* officially documented in the "lib" help page. For example, 
imagine that a library has just been built (e.g. the plotlib...)


genlib('plotlib','macros')

I need to add to this library %axesData_i_h which is a clone of 
generic_i_h (in overloadinglib), which can be done in scilab<6.x by:


%axesData_i_h=generic_i_h;
save('macros/%axesData_i_h.bin',%axesData_i_h)
mputl([mgetl('macros/names');'%axesData_i_h'],'macros/names')

I said above "not clean at all", because the binary file "macros/lib" 
(which is created by the genlib call) does not need to be updated, as 
a subsequent


plotlib=lib("macros")

loads all functions, including %axesData_i_h


Doing things like this is not possible any more. It was was also to 
add persistent variables in libraries, with the same mechanism.


By the way, under scilab 6.0.1, the "macros/lib" is now an XML file 
with a clear syntax, e.g.




  md5="d0966468b335a69681a29d84c99feb5c"/>
  md5="a1ebda57a1607b28095def2e415e2ec1"/>

...


It does not seem to be documented either.

S.






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



--
Stéphane Mottelet
Ingénieur de recherche
EA 4297 Transformations Intégrées de la Matière Renouvelable
Département Génie des Procédés Industriels
Sorbonne Universités - Université de Technologie de Compiègne
CS 60319, 60203 Compiègne cedex
Tel : +33(0)344234688
http://www.utc.fr/~mottelet

--
Stéphane Mottelet
Ingénieur de recherche
EA 4297 Transformations Intégrées de la Matière Renouvelable
Département Génie des Procédés Industriels
Sorbonne Universités - Université de Technologie de Compiègne
CS 60319, 60203 Compiègne cedex
Tel : +33(0)344234688
http://www.utc.fr/~mottelet

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

Re: [Scilab-users] clone a function in a library

[Samuel Gougeon]

Le 28/02/2018 à 15:17, Samuel Gougeon a écrit :
Another way would be to clone the source file with a hard link with 
your OS.
It is possible with Linux. It should be possible with powershell under 
Windows.

With MacOS, i don't know. Likely possible as well. Could you confirm?
Then, try genlib() and see if it considers such a link..
In Linux, it should : all inodes are equal
In Windows: I will try, when updating the lib() and genlib() pages


But it should be portable. I don't think that hard links are so..
As long as the library is not recompiled by the user, it should work.
Otherwise, hard links should be set in the module builder, before 
building the library, and according to the OS...


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

Re: [Scilab-users] clone a function in a library

[Samuel Gougeon]

Another way would be to clone the source file with a hard link with your OS.
It is possible with Linux. It should be possible with powershell under 
Windows.

With MacOS, i don't know. Likely possible as well. Could you confirm?
Then, try genlib() and see if it considers such a link..
In Linux, it should : all inodes are equal
In Windows: I will try, when updating the lib() and genlib() pages

Samuel


Le 28/02/2018 à 14:52, Stéphane Mottelet a écrit :

Hello,

With the new library system, it is no longer possible to clone a 
function in a library. This feature is still documented in the help 
page of "lib" but is not working anymore since saving a user-defined 
scilab function uses the sod/hdf5 format. Maybe one can ask why such a 
feature is needed ? Sometimes it can be usefull to have a function 
which is callable by different names but actually does the same thing. 
The different calling names can come from the adaptation for different 
types of data, which can sometimes lead to the same treatment, hence 
to the same function. Instead of writing two functions with the same 
source code but a different calling name, cloning the original one was 
an interesting feature.


I admit that the way it worked under scilab<6.x was not clean at all 
*but* officially documented in the "lib" help page. For example, 
imagine that a library has just been built (e.g. the plotlib...)


genlib('plotlib','macros')

I need to add to this library %axesData_i_h which is a clone of 
generic_i_h (in overloadinglib), which can be done in scilab<6.x by:


%axesData_i_h=generic_i_h;
save('macros/%axesData_i_h.bin',%axesData_i_h)
mputl([mgetl('macros/names');'%axesData_i_h'],'macros/names')

I said above "not clean at all", because the binary file "macros/lib" 
(which is created by the genlib call) does not need to be updated, as 
a subsequent


plotlib=lib("macros")

loads all functions, including %axesData_i_h


Doing things like this is not possible any more. It was was also to 
add persistent variables in libraries, with the same mechanism.


By the way, under scilab 6.0.1, the "macros/lib" is now an XML file 
with a clear syntax, e.g.




  md5="d0966468b335a69681a29d84c99feb5c"/>
  md5="a1ebda57a1607b28095def2e415e2ec1"/>

...


It does not seem to be documented either.

S.




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

Re: [Scilab-users] clone a function in a library

[Samuel Gougeon]

Hello Stéphane,

I would try the following:
After genlibing the set of regular .sci files,
* save the clone with
   save('macros/%axesData_i_h.bin', "%axesData_i_h")
* add a line in the lib file



The MD5 hash is of the content of the .sci file, that here does not 
exist. It is use by genlib to check whether the .sci must be recompiled 
or not. You may try to set any md5 (or the cloned one). As long as you 
don't recompile the lib with genlib -- just loading it with load() or 
lib() --, this should work.


My 2 cents..

Samuel


Le 28/02/2018 à 14:52, Stéphane Mottelet a écrit :

Hello,

With the new library system, it is no longer possible to clone a 
function in a library. This feature is still documented in the help 
page of "lib" but is not working anymore since saving a user-defined 
scilab function uses the sod/hdf5 format. Maybe one can ask why such a 
feature is needed ? Sometimes it can be usefull to have a function 
which is callable by different names but actually does the same thing. 
The different calling names can come from the adaptation for different 
types of data, which can sometimes lead to the same treatment, hence 
to the same function. Instead of writing two functions with the same 
source code but a different calling name, cloning the original one was 
an interesting feature.


I admit that the way it worked under scilab<6.x was not clean at all 
*but* officially documented in the "lib" help page. For example, 
imagine that a library has just been built (e.g. the plotlib...)


genlib('plotlib','macros')

I need to add to this library %axesData_i_h which is a clone of 
generic_i_h (in overloadinglib), which can be done in scilab<6.x by:


%axesData_i_h=generic_i_h;
save('macros/%axesData_i_h.bin',%axesData_i_h)
mputl([mgetl('macros/names');'%axesData_i_h'],'macros/names')

I said above "not clean at all", because the binary file "macros/lib" 
(which is created by the genlib call) does not need to be updated, as 
a subsequent


plotlib=lib("macros")

loads all functions, including %axesData_i_h


Doing things like this is not possible any more. It was was also to 
add persistent variables in libraries, with the same mechanism.


By the way, under scilab 6.0.1, the "macros/lib" is now an XML file 
with a clear syntax, e.g.




  md5="d0966468b335a69681a29d84c99feb5c"/>
  md5="a1ebda57a1607b28095def2e415e2ec1"/>

...


It does not seem to be documented either.

S.




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

Re: [Scilab-users] "intg" and i"ntegrate"

[fujimoto2005]

Dear Samuel.
Thank for your advice.
I will fill in a wish report on Bugzilla.

Best regards.




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

[Scilab-users] clone a function in a library

[Stéphane Mottelet]

Hello,

With the new library system, it is no longer possible to clone a 
function in a library. This feature is still documented in the help page 
of "lib" but is not working anymore since saving a user-defined scilab 
function uses the sod/hdf5 format. Maybe one can ask why such a feature 
is needed ? Sometimes it can be usefull to have a function which is 
callable by different names but actually does the same thing. The 
different calling names can come from the adaptation for different types 
of data, which can sometimes lead to the same treatment, hence to the 
same function. Instead of writing two functions with the same source 
code but a different calling name, cloning the original one was an 
interesting feature.


I admit that the way it worked under scilab<6.x was not clean at all 
*but* officially documented in the "lib" help page. For example, imagine 
that a library has just been built (e.g. the plotlib...)


genlib('plotlib','macros')

I need to add to this library %axesData_i_h which is a clone of 
generic_i_h (in overloadinglib), which can be done in scilab<6.x by:


%axesData_i_h=generic_i_h;
save('macros/%axesData_i_h.bin',%axesData_i_h)
mputl([mgetl('macros/names');'%axesData_i_h'],'macros/names')

I said above "not clean at all", because the binary file "macros/lib" 
(which is created by the genlib call) does not need to be updated, as a 
subsequent


plotlib=lib("macros")

loads all functions, including %axesData_i_h


Doing things like this is not possible any more. It was was also to add 
persistent variables in libraries, with the same mechanism.


By the way, under scilab 6.0.1, the "macros/lib" is now an XML file with 
a clear syntax, e.g.




  md5="d0966468b335a69681a29d84c99feb5c"/>
  md5="a1ebda57a1607b28095def2e415e2ec1"/>

...


It does not seem to be documented either.

S.


--
Stéphane Mottelet
Ingénieur de recherche
EA 4297 Transformations Intégrées de la Matière Renouvelable
Département Génie des Procédés Industriels
Sorbonne Universités - Université de Technologie de Compiègne
CS 60319, 60203 Compiègne cedex
Tel : +33(0)344234688
http://www.utc.fr/~mottelet

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

[Scilab-users] Scilab and hdf5 format (small survey)

[paul . carrico]

Hi All  

I'm playing with hdf5 format into Scilab (I'm currently in an early
stage that consists in understanding what the structures are); the goal
is to deal with huge amount of data coming from Finite Element Analyses,
and to perform additional calculations. 

I'm wondering if there are a lot of people working with Hdf5 file into
Scilab? in what fields? 

(behind this, a goal among others  is to get feedbacks from them on
advantages and disadvantages). 

Regards 

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