<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hello Yann,<br>
<br>
Why not starting from Serge Steer's proposal and discussing it:<br>
<a class="moz-txt-link-freetext" href="http://bugzilla.scilab.org/14239">http://bugzilla.scilab.org/14239</a><br>
Actual proposal: <a class="moz-txt-link-freetext" href="http://bugzilla.scilab.org/attachment.cgi?id=4184">http://bugzilla.scilab.org/attachment.cgi?id=4184</a><br>
<br>
In a general case, the only thing i would say about it (as about
any other one), is that<br>
no subsection should have less that 4-5 entries. For proposed
sub(-sub)sections with<br>
less than 4 entries, these ones should be transfered at the root
of the parent section.<br>
E.g.:<br>
<pre>Control Design
/Linear quadratic
gcare
... ~10 entries : OK
/Pole placement
kpure
krac2
ppol
stabil
<strike>/Tracking</strike>
<font color="#3333ff">gfrancis </font> NOK
<strike>/Disturbance decoupling</strike>
<font color="#3333ff"> ddp </font> NOK
/H-infinity
ccontrg
dhinf
dhnorm
... > 5 entries : OK
</pre>
<b>should rather be</b><br>
<pre>Control Design
/Linear quadratic
gcare
... ~10 entries : OK
/Pole placement
kpure
krac2
ppol
stabil
/H-infinity
ccontrg
dhinf
dhnorm
... > 5 entries : OK
<font color="#3333ff">gfrancis
ddp</font>
</pre>
<br>
For my part, i hate loosing my time in exploring deep levels
having almost nothing. <br>
From having for years not a single subsection with 140 functions
on the same common box, to having too many subsections poorly
populated, i think there is a wise middle way.<br>
If further functions are implemented and may feed a new common
subsection, then it will never be too late to create it later when
really needed and meaningful.<br>
<br>
Best regards<br>
Samuel<br>
<br>
Le 18/04/2016 20:08, Yann DEBRAY a écrit :<br>
</div>
<blockquote cite="mid:5715229F.50902@scilab-enterprises.com"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
Hello Scilab user, <br>
<div class="moz-forward-container"><br>
We would like to develop Scilab further in specific fields such
as <b>Control System</b> and that starts by making Scilab
features clearer. For now the <a moz-do-not-send="true"
href="https://help.scilab.org/docs/5.5.2/en_US/section_46d43fa43588512dc7dc2c3d190b775b.html">Scilab
online help</a> is quite hard to operate. So, we are beginning
to organize it starting with the control system (<a
moz-do-not-send="true"
href="https://help.scilab.org/docs/5.5.2/en_US/section_64a8529216e858b335b0e6c058385350.html">CACSD</a>)
features. Here is a first shot:<br>
<br>
<strong>LTI model generation and manipulation</strong><br>
# Discrete and continuous time<br>
# State-space and transfer function representations<br>
<strong>Analyzing model</strong><br>
# Evans for root locus<br>
# Steady state error<br>
# Bode, Nyquist and Black<br>
# Time, frequency response<br>
<strong>Designing and tuning control systems</strong><br>
#PID, LQG tuning<br>
<br>
It is incomplete and obviously superficial. That is why we need
a competent opinion.<br>
--> Please give us feedback about how you would like it to be
organized ;)<br>
<br>
Yann Debray<br>
For the Scilab Team<br>
<br>
</div>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:users@lists.scilab.org">users@lists.scilab.org</a>
<a class="moz-txt-link-freetext" href="http://lists.scilab.org/mailman/listinfo/users">http://lists.scilab.org/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</body>
</html>