<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hello Sylvestre,<br>
<br>
Taking some time to read completely the SEP, i would have some
remarks<br>
on some specific points of it:<br>
<br>
* (head of page 2)
<meta http-equiv="CONTENT-TYPE" content="text/html;
charset=ISO-8859-1">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.2 (Win32)">
<style type="text/css">
<!--
@page { margin: 2cm }
P { margin-bottom: 0.21cm; background: transparent; line-height: 150%; text-align: justify; page-break-before: auto }
P.western { font-size: 10pt; so-language: en-US }
P.cjk { font-size: 10pt }
--: </style><b><font color="#3333ff"><span style="font-style: normal;"><span
style="font-weight: normal;">Several
“types” are based on </span></span><span
style="font-weight: normal;">tlist</span><span
style="font-style: normal;"><span style="font-weight: normal;">
or </span></span><span style="font-weight: normal;">mlist</span><span
style="font-style: normal;"><span style="font-weight: normal;">.
It is the case of </span></span><span style="font-weight:
normal;">rational</span><span style="font-style: normal;"><span
style="font-weight: normal;">,
</span></span><span style="font-weight: normal;"></span></font><br>
<font color="#3333ff"><span style="font-weight: normal;">state-space</span><span
style="font-style: normal;"><span style="font-weight: normal;">,
</span></span><span style="font-weight: normal;">hypermat</span><span
style="font-style: normal;"><span style="font-weight: normal;">
and </span></span><span style="font-weight: normal;">struct</span><span
style="font-style: normal;"><span style="font-weight: normal;">.</span></span><span
style="font-style: normal;"><span style="font-weight: normal;">They
are
therefor transparently saved.</span></span></font></b>
<br>
=> What about the missing <i>cell</i> datatype ? (this one is
presently also a predefined mlist() type, <br>
isn't it? But there will be some changes in Scilab 6 about cells.
So...a new full type?)<br>
<br>
* (2 lines before 3.2)<i> <font color="#3333ff">If the variable is
</font><font color="#3333ff">primitive and without
complex values associated, ...</font></i>
<meta http-equiv="CONTENT-TYPE" content="text/html;
charset=ISO-8859-1">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.2 (Win32)">
<style type="text/css">
<!--
@page { margin: 2cm }
P { margin-bottom: 0.21cm; background: transparent; line-height: 150%; text-align: justify; page-break-before: auto }
P.western { font-size: 10pt; so-language: en-US }
P.cjk { font-size: 10pt }
--></style>
<br>
By <i>primitive</i>, you are not speaking about a pointer to a
primitive (function), are you?<br>
<br>
* 3.2.1 Example. After the screenshot of the table, you mention
<meta http-equiv="CONTENT-TYPE" content="text/html;
charset=ISO-8859-1">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.2 (Win32)">
<style type="text/css">
<!--
@page { margin: 2cm }
P { margin-bottom: 0.21cm; background: transparent; line-height: 150%; text-align: justify; page-break-before: auto }
P.western { font-size: 10pt; so-language: en-US }
P.cjk { font-size: 10pt }
--></style><font color="#ff0000"><font color="#3333ff"><i>hdfview</i></font>.</font>
<br>
Is it a new editor, distinct from <i>browsevar</i> ? Couldn't
browsevar be extended, <br>
instead of being bypassed/duplicated?<br>
<br>
* (the main concern) In 3.3, you describe the specific role of the #
char. <br>
Now, # in an authorized heading as well as building char in names of
variables.<br>
Couldn't this be of concern, for instance when "decoding" the
nesting level of<br>
hierarchical data with names including some #?<br>
<br>
* 3.3.1 sparse (1 line before 3.3.2:
<meta http-equiv="CONTENT-TYPE" content="text/html;
charset=ISO-8859-1">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.2 (Win32)">
<style type="text/css">
<!--
@page { margin: 2cm }
P { margin-bottom: 0.21cm; background: transparent; line-height: 150%; text-align: justify; page-break-before: auto }
P.western { font-size: 10pt; so-language: en-US }
P.cjk { font-size: 10pt }
--></style><font size="2"><i><br>
<big>#2# </big><big>reference a matrix of <u>double</u> which
contains 1.0; 3.0; 2.0</big></i></font>
<br>
=> (i am underlying) Apparently, sparse with <i>complex</i>
numbers won't be supported.<br>
Do you confirm that?<br>
<br>
* 3.3.2 Boolean sparse: A typo:<br>
<meta http-equiv="CONTENT-TYPE" content="text/html;
charset=ISO-8859-1">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.2 (Win32)">
<style type="text/css">
<!--
@page { margin: 2cm }
TD P { margin-bottom: 0cm }
TD P.western { font-size: 11pt; so-language: en-US }
TD P.cjk { font-size: 10pt }
P { margin-bottom: 0.21cm }
--></style><big><font size="2"><big><i><span style="font-style:
normal;"><span style="font-weight: normal;"> While
a sparse has 3 datasets, the</span></span></i><span
style="font-style: normal;"><span style="font-weight:
normal;"><i> sparse has only 2 ...</i><br>
=> </span></span></big></font><font size="2"><big><span
style="font-style: normal;"><span style="font-weight:
normal;">While
a sparse has 3 datasets, the</span></span><span
style="font-style: normal;"><span style="font-weight:
normal;"> boolean sparse has only 2...</span></span></big></font></big>
<p class="western" align="LEFT" lang="en-US"><big>
</big></p>
That's all for me ;-)<br>
<br>
Best regards<br>
Samuel<br>
<br>
<br>
----- Message d'origine ----- <br>
De : Sylvestre Ledru <br>
Date : 25/05/2011 00:00:
<blockquote cite="mid:1306274430.20538.6.camel@losinj.inria.fr"
type="cite">
<pre wrap="">Le lundi 23 mai 2011 à 17:47 +0200, Sylvestre Ledru a écrit :
</pre>
<blockquote type="cite">
<pre wrap="">Hello,
Since Scilab 5.2.0, we introduced a HDF5 storage for Scilab variables.
It is already widely used in the Xcos internal.
HDF5 is now a de-facto standard for the storage of numerical data [1].
In Scilab 5.4.0, we are going to update the load/save functions to use
this format (it is going to be the SEP 065). This for two main reasons:
* for the future version 6.0 of Scilab (which won't manage current .bin
files)
* allows the management of Scilab data (import/export) files by other
software.
The attached document shows the current specification and implementation
of the Scilab / HDF5 schema.
</pre>
</blockquote>
<pre wrap="">For information, this SEP is incomplete. It will be updated once we will
completed the support of handlers (including uicontrol & uimenu).
Sylvestre
</pre>
</blockquote>
<br>
</body>
</html>