Hello Antoine, hello all,
The www.scilab.org website have not been updated yet but the nightly builds
might be removed in
favor of the Continuous Integration builds [1]. The MacOs build [2] is a bit
unreliable but might
provide your the latest binaries.
[1]:
Hello Philippe,
Not really a technical point, but about your comment on :
> I am very disappointed that the owner (scilab enterprises) of a great
> application like scilab did
> not succeeded to maintain a working version of the application.
As you may probably know, free software is a hard
Hello Christian, Samuel,
My 2c, most of the modern languages supporting such a feature are using the
one-character variable
trick; sometimes enforced by conventions. For example, Go, Rust and Python are
using `_` as in :
[_,_,kb] = intersect(grand(1,10,"uin",0,9), grand(1,10,"uin",0,9));
This
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
Dear users,
The bugzilla / codereview server will be migrated to our new ESI-backed
infrastructure. These
services will be down for 24 to 48 hours ; we will do our best to minimize the
down time.
If you wish to submit a patch, please mail it to the dev mailing list.
Sorry for the
name a few functions that are problematic.
>
> With Regards,
> Brijesh Gupta C R
>
> On Wed, Sep 6, 2017 at 7:13 PM, Clément David <clement.da...@esi-group.com>
> wrote:
> > Hello Abhinav,
> >
> > Nice to have someone interested in sci
Hello Abhinav,
Nice to have someone interested in scilab2c. Currently there is no active
maintainer, feel free to
contribute to it.
> 1) To write a new function, we always have to decide the output sizes
> according to scalar inputs
> or size of input matrix. But, if our output size depends on
Dear users,
The migration is complete for this server. Do not hesitate to report any issue
on
https://bugzilla.scilab.org / Scilab websites product.
Thanks for your patience,
--
Clément
Le mercredi 30 août 2017 à 09:04 +, Clément David a écrit :
> Dear users,
>
> The mailing li
Dear users,
The mailing list server will be migrated to our new ESI-backed infrastructure.
The lists will be
down for 24 to 48 hours ; we will do our best to minimize the down time.
Sorry for the inconvenience,
--
Clément
___
users mailing list
Dear users,
Some of our servers are currently down due to power outage !
Thanks for your patience,
--
Clément
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users
Hello Hermes,
> There were also differences
> with the Block GAINBLK vs. GAINBLK_f. I think this does not make the
> differences in results. Correct?
These blocks only differs in their parameter settings. The behavior is the same
and the simulation
results should be similar.
--
Clément
Hello Hilall,
I suppose you are using Scilab 5.5.2 ; it is the last Java 1.6 Scilab supported
version. What's your
OS ?
--
Clément
Le dimanche 20 août 2017 à 12:24 +0800, Hilaal Alam a écrit :
> Hi
>
> I have been using Scilab for a decade. Suddenly I updated JAVA for my other
> project and
Hello,
The compilation chain seems to have been locked for some days due to the
infrastructure migration.
Please report an issue on bugzilla.scilab.org website section to publicly track
this issue.
Thanks,
--
Clément
Le lundi 21 août 2017 à 02:31 -0700, Hermes a écrit :
> I tried to access
Hello Sanchayan and welcome,
The Scilab software is basically composed of :
1. an interpreter coded in C++
2. a graphical user interface coded in Java
3. mathematical functions coded in C / C++ / Fortran
If you want to start, you could get through a bug in bugzilla.scilab.org and
try to fix
Hi,
You could still use `atomsInstall foo.zip` to install a binary module. To
download it, use the link
within the atoms.scilab.org website.
Thanks,
--
Clément
Le jeudi 03 août 2017 à 16:42 +0800, innama ana mundzir a écrit :
> Hi,
>
> I want to download backdoor module but the download link
Hi,
It seems to be a known bug, http://bugzilla.scilab.org/show_bug.cgi?id=15050
could you confirm ?
Thanks,
--
Clément
Le mercredi 02 août 2017 à 23:31 -0700, Hermes a écrit :
> I seem to be unable to create supberblocks. When I select a group of blocks
> Xcos creates a superblock. But that
Hello Shamika,
Scilab 6 C API only use scilabEnv variable ; pvApiCtx is used for Scilab 5 and
6 stack-like C API.
Mixing API should be avoided, if you are porting from 5 to 6 and require some 6
features (mlist,
struct, high-performance, etc..) I suggest you to only use the new 6 API !
Thanks,
Hello Luc,
scilab.io is used to retrieve Scilab news ; if the current behavior does not
feel your needs please
open a bug on bugzilla.scilab.org .
Regards,
--
Clément
Le mardi 30 mai 2017 à 10:46 +, Hermitte Luc (CS SI) a écrit :
> Hi,
>
> I'm trying to install scilab on our cluster, but
Hello,
Thanks for these information, as you wrote the save / load bug might be related
to your system. Are
you using a specific system locale / languages ?
--
Clément
Le mardi 30 mai 2017 à 03:52 -0700, arwooldridge a écrit :
> Having similar problems with xcos on scilab 6.0.0 with windows 7
Thanks Samuel for the in-depth understanding of how ATOMS works and the patch.
I merged it after a
small edit on the test.
--
Clément
Le mardi 30 mai 2017 à 08:05 +0200, Samuel Gougeon a écrit :
> I did something before posting that removed a step of the how-to . Here it is
> restored:
>
> Le
Hello,
You could take a look at inside Scilab source code ; the source code for
fortran blocks are located
in
http://gitweb.scilab.org/?p=scilab.git;a=tree;f=scilab/modules/scicos_blocks/src/fortran
.
Thanks,
--
Clément
Le vendredi 19 mai 2017 à 01:29 -0700, planetcooler a écrit :
> Can
you
> just give me the right section where to report the bug (java or scilab
> or anything else) ?
>
> Thanks,
>
> Florian.
>
>
> On 03/05/17 12:02, Clément David wrote:
> > Hello Florian,
> >
> > Thanks for this information ; could you please open a bug w
Hello Antoine, Nikolay,
The selection of a much performant BLAS / LAPACK implementation is very
system-dependent and I don't
want to maintain something not standard / widely deployed on Linux
distributions. As a reference,
the current Fedora status is to link against the library used at
Hello Michael,
Even if it can be frustrating, please keep the discussion on
https://bugzilla.scilab.org/show_bug.cg
i?id=14698 rather than spamming the users ML. This users ML is dedicated to
community knowledge
sharing and is not a way to contact us.
AFAIK there is no workaround and it is not
Hello Kandy,
Are you using the Scilab 6.0.0 version or another one ? Could give more
information about your
system : which OS ? hardware ?
Thanks,
PS: I suggest you to open a bug on bugzilla.scilab.org to ease communication on
that issue. Users ML
is more usage oriented.
--
Clément
Le
Hi Phillip,
On the scope, there is a "Buffer size" parameter which will define the
specified period to store on
the data.
Note that during a simulation you are producing a lot of values, be sure to
define it accordingly to
the period you want to observe.
--
Clément
Le jeudi 06 avril 2017 à
Hi Paul,
The Scilab "coverage" tools can be used to explore existing codes. Currently it
only supports an
HTML (for code, measurements) and "binary" backend but we can easily add a
"Graphviz" or "Callgrind"
backend to display call graphs.
IMHO this could be also good to describe your needs in
Hello Chin Luh,
Thanks for reporting that, it seems to be a bug on our side ; could your report
it please ?
--
Clément
Le mercredi 22 mars 2017 à 11:54 +0800, Tan Chin Luh a écrit :
> Hi,
>
> Just to check whether anyone encounter issues with the atomsTest function.
>
> When running the
Hi Pierre,
Nice catch, could you open a bug on that ?
The bug is also much more understandable with :
a = mlist(['mytype']);
b = mlist(['myothertype']);
function out = %mytype_e(varargin)
var = varargin($);
field = varargin(1);
disp(typeof(varargin))
disp(typeof(var))
Hi Dirk,
Nice catch ! There might be an issue on page generation, I will check it today.
Thanks,
--
Clément
Le mardi 07 mars 2017 à 15:29 +0100, Dirk Reusch a écrit :
> Hello,
>
> Why are the nightly builds of Scilab Branch 6.0 - 64 bits for GNU/Linux
> on scilab.org not up-to-date like for
refered language for production codes.
>
> Thanks
>
> 2017-03-06 14:28 GMT-03:00 <sho...@energetiq.com>:
> I had looked up SWIG. I have found no examples of connecting fortran to
> scilab using swig.
> Clément David ---03/06/2017 03:54:24 AM---> While I'm
Hi Eduardo,
You should pass the `--disable-static-system-lib` flag to the configure script.
This was an options
added to ensure we ship with the libstdc++ instead of using the system one. It
should only be used
if you plan to distribute the scilab binary in old system (eg. without a C++11
Hi Amanda,
Le jeudi 02 mars 2017 à 18:24 -0300, Amanda Osvaldo a écrit :
> Just a note about performance in computing.
>
> I read the Intel articles in Intel Developer Zone and frequently they call to
> think about the
> limitations in the memory cache and the set of instructions used to do the
> While I'm on the subject, the old Intersci system was a very convenient way
> to automatically
> generate the interface routine between scilab and an arbitrary fortran
> subroutine. There seems
> not to be recent documentation on doing the same (specifically for fortran).
> Or am I missing
Hi Pierre,
Le jeudi 02 mars 2017 à 22:12 +0100, Pierre Vuillemin a écrit :
> Concerning speed, while I agree that this is often not that important, the
> Julia Language has
> demonstrated that it is not necessarily unreachable for a "high level
> language". I guess it mainly
> relies on the
Hello,
Yes exactly Pierre, 'r' means rows and 'c' means columns :) .
--
Clément
Le mercredi 01 mars 2017 à 01:02 -0700, PirPyn a écrit :
> I did not understant well your question. But from the size() help :
>
> Scilab wrote
> > The syntax n = size(x, sel) may be used to specify what dimension
Hi Samuel,
This is clearly a regression : there probably some synchronization issue (CPUs
are not busy at all),
could you report a bug on it please ?
--
Clément
Le samedi 25 février 2017 à 18:05 +0100, Samuel Gougeon a écrit :
> Hello,
>
> Opening a new empty figure (without drawing anything)
Hi Stefan,
Le jeudi 23 février 2017 à 15:47 +0100, Stefan Du Rietz a écrit :
> I will first tell you some odd things. It appeared that Scilab 5.5.2
> had got exactly the same issue in this computer (I had not used it for
> a while)! I know that the only changes since I last used it were,
>
Hi Stefan, Lester,
I confirmed the issue (0.02s in 5.5.2 vs 6.90 in 6.0.0) and on a local build I
am able to trace the
issue using the Linux perf tool:
+ 58,69%58,68% libsciast.so.6.0.0 [.]
types::getIndexesWithDims
+ 22,09%22,08% libsciast.so.6.0.0
Hi Reinaldo,
> Thank you for your mail. I downloaded the Command Line Tool as suggested by
> Paul in my Mac. It
> works! I found out that "gcc" and "g++" are symlinks and they are not "real"
> compiler because
> there is no entry for "man gcc" in Mac OSX. The real name is Clang and
>
Hi Mehran,
> We all know it wasn't as easy as it looked. So my warmest thanks to all the
> folks who engaged to make Scilab fresher and stronger.
> I wanna take my hat off to them all right here. :-)
Thanks for clarifying things :), indeed it was not easy to replicate behaviors
implemented 20
Hi Stefan,
Could you open a bug with all your system information please ?
As you might known, we not only build scilab but also pass the tests on the
binary version using a
set of different machines before releasing. This is likely a bug in your local
configuration (either
graphical card or
Hi Reinaldo and welcome,
Yes Paul is right and just for completness (and CC-ing dev) :
We currently do not require an IDE to build Scilab ; you can program using vim
/ emacs / notepad++,
gcc / clang / msbuild. As common IDEs provide a way to import an exiting code
base as a new project,
we
Hello,
This "SCI/contrib/toolbox_skeleton.iss" file comes from the Scilab source tree
and is used on the
Scilab installer to manage toolbox_skeleton and xcos_toolbox_skeleton files. It
is not really useful
out of Scilab.
*AND*
A "toolbox_skeleton_redist.iss" file is available on the
Hi Samuel,
This change is probably not intentional, could you post a bug on that please ?
PS: even if the type "mc" as been clarified as "function", we can add a
compatibility mode for
overloading aliases.
--
Clément
Le lundi 19 décembre 2016 à 08:41 +0100, Samuel Gougeon a écrit :
> Hello
Just to close the thread, there is bug reports on that:
"loading a SOD Scilab v6 file in Scilab 5"
http://bugzilla.scilab.org/show_bug.cgi?id=14745
"V6 crashes when trying to load() a file saved with save() in 5.3.3"
http://bugzilla.scilab.org/sho
w_bug.cgi?id=14840
--
Clément
Le lundi 14
Hello Philipp,
AFAIK the only way to get this kind of direct memory access is only performed
by GL debuggers. I
personally use APITrace [https://github.com/apitrace/apitrace] to debug GL
things but it does not
allow a memory view (only function call tracing).
--
Clément
Le lundi 07 novembre
Hello Tim,
Thanks for the report, FYI I checked a Scilab 6 local build and a Scilab 5.5.2
on Ubuntu 16.04 and
it seems to works (at least plot3d works).
I suggest you to reboot and trying to report your issue to Ubuntu on glxgear
(which is the right 3D
testing tool).
--
Clément
Le vendredi
Hello,
Yes sorry about that, these e-mail have been awaiting for an admin review but
we currently have no
more a dedicated ressource on that so there might be some delay (sorry about
that).
I and Cédric have the full admin access but most of the S/E employees are able
to accept mails. I
have
Hallo Frieder,
Most of this ML readers / writers are not german speaker, could you please use
english next time ?
Thanks,
--
Clément
Le jeudi 06 octobre 2016 à 15:18 +0200, Frieder Nikolaisen a écrit :
> Hallo Jens,
>
> danke schön. Die Testmatrix ist Unsinn. Somit weiß ich nun, dass der
>
Hello Paul,
Thanks for asking after Tim remark on specialized content. To clarify, I would
like to give some
general advices about this ML.
IMHO This ML is good for general Scilab / Scientific questions across domains
covered by the Scilab
software. For very specific questions, it might be
Hello Paul,
Thanks for your comment. The Scilab 6 version does not have a memory limitation
anymore *but*,
depending on the algorithm you applied, you might not notice that.
Could you detail your use-case please ?
What "does not work" ?
Is it crashing ?
Do you have an error ?
FYI the new
Hi all,
Nice content on https://wiki.scilab.org/FromScilab5ToScilab6 ; I will add a
link to it on the more
formal CHANGES.md file. As advanced user, do not hesitate to add content on
this wiki page ; it can
be edited by any registered user.
Thanks,
--
Clément
Le mercredi 28 septembre 2016 à
Hello Gerhard,
Great question ! Use the toolbox_skeleton [1] and create you own Scilab toolbox
to easily re-use you
own function set. It might be automatically loaded at Scilab startup and used
by your scripts.
First, simply create a directory "myToolbox" and a sub-directory "macros". Put
all
Hello PhilAPol,
The `pvApiCtx` variable has been introduced to migrate between Scilab 5 and
Scilab 6. What Scilab
version are you using ?
--
Clément
Le jeudi 14 juillet 2016 à 17:37 -0700, PhilAPol a écrit :
> I am using Visual Studio Express 2015 with C++ and attempted to build the cpp
>
Hello Philippe,
About replacing "%foo_" to "foo_" in a file, I crafted an example using
strsplit() and strcat() (see
attached) but it might be good to have an extended strsubst() that can output
groups (\1 in your
regexp).
Do not hesitate to report a bug on that,
--
Clément
Le mercredi 29
Hello Grzegorz,
This seems to be a memory leak somewhere, could you check that your `udp_recv`
gateway does not
leak. On our side, if you do not append to buffer nothing should leak.
To check that the Java render is correct, you could connect to the Scilab JVM
using VisualVM [1] and
check the
Hello Pierre, hello all,
Great notice and, indeed, everything is fine !
As Scilab 6.0.0 is not released yet, it is not branched on a dedicated "6.0"
branch and we are still
developing on the "master" branch. The compilation chain produce each night a
new nightly build
containing all changes
Hello Pierre,
After some manual cleanup on the build machine, everything was right
this night : see http://www.scilab.org/en/development/nightly_builds/ma
ster
Thanks for the report,
--
Clément
Le mercredi 29 juin 2016 à 08:57 +0200, Clément David a écrit :
> Hello Pierre,
>
&g
Hello Nicolay,
Le vendredi 24 juin 2016 à 23:30 +0300, Nikolay Strelkov a écrit :
> Do you plan to increase passed tests quantity in Xcos 6.0.0?
Well you spot it well, "xcos" might probably be the module with the
poor test ratio. Some the tests are still failing due to warning
messages but
Hello Pierre,
Thanks for the ping, a fix is in review at https://codereview.scilab.org/18287 .
Note that the bug is just a rendering bug and does not impact simulation values.
Regards,
--
Clément
Le lundi 20 juin 2016 à 19:25 +0200, Perrichon a écrit :
> Dear,
>
> With Scilab-Xcos 6.0.0
Hello Umut,
This display setting is preset without any length restriction. I guess you
should post a bug to
explicit this request. I guess a reasonable implementation would be to limit
the number of displayed
char accordingly to the block bounds (to avoid any char out of the block
bounds).
Hello Umut,
All Scilab facilities are designed to work for "external modules" or
"toolboxes". The
toolbox_skeleton (shipped with scilab) provide such a standard organization
with tests. Just use :
test_run('path_to_my_toolbox');
Each test is a Scilab script and you can use special
Hello,
I guess there might be a bug on that support. You can add yourself to the CC
list on the bugzilla
interface to be alerted on change.
--
Clément
Le dimanche 03 avril 2016 à 06:04 -0700, jaipur a écrit :
> Thank you.
> I understand that scilab 6.0.0-beta-1 does not support Mac OS X El
Hello Jasper,
Yes it should be *but* this is not 100% guarantee. We tried to avoid any
breakage during the alpha
to beta transition on gateways but preferred to have a better 6.0.0 API on the
beta.
The reason of the C_GATEWAY_PROTOTYPE to STACK_GATEWAY_PROTOTYPE conversion is
that we
And also, use the g...@lists.scilab.org for GSoC related communication :) .
--
Clément
Le mardi 22 mars 2016 à 20:50 +0530, Lahiru Dilshan a écrit :
> Thanks Clement. I'll try this project. I'll start to write the proposal.
>
> On Tue, Mar 22, 2016 at 7:16 PM, Clément David
>
u sure that the Java Script API is not selected in GSoC this year?
> https://wiki.scilab.org/GSoC_project_proposal link shows the project ideas of
> Scilab and the Java
> Script API project is there.
>
> On Tue, Mar 22, 2016 at 1:00 PM, Clément David
> <clement.da...@scilab-enterprise
interested in Java
> Scripting Api and Anonymous
> Usage Tracking projects.
> So, can u give me more details about those projects which one is the high
> priority this year?
>
> Thanks.
>
> On Mon, Mar 21, 2016 at 9:50 PM, Clément David
> <clement.da...@scilab-e
in\bin;C:\Program!
> ! Files (x86)\AMD\ATI.ACE\Core-
> Static !
> !
>
> !
> !ComSpec:
> C:\Windows\system32\cmd.exe
> !
> !
&
Hi,
Please post a detailed bug with all these information and your configuration.
We usually only check
the dynamic linking feature with a reduced set of compilers and your
configuration might be a not
checked one .
Thanks in advance,
--
Clément David
Le mardi 15 mars 2016 à 16:09 +0800
Hi Tan,
Thanks for the information ; this is already fixed [1] ;) do not hesitate to
post a bug on
bugzilla.scilab.org next time.
[1:]
http://gitweb.scilab.org/?p=scilab.git;a=commit;h=064a1839fb0a501e4ff05ca23b25c2cd618be1aa
Regards,
--
Clément David
Le lundi 14 mars 2016 à 09:34 +0800
Hello Mayank and welcome,
Firstly, to communicate on the GSOC we use a dedicated ML g...@lists.scilab.org
; please use it next
time.
Then about the JOGL issue while building, I strongly suggest you to use the
Prerequirement SVN [1]
instead of libraries and JARs provided on your system. The
Hi Ilie and welcome,
For the GSoC, we use a dedicated mailing-list to ease integration on the
community and to help
student discover how we work. Please next time post to : g...@lists.scilab.org .
As you might have already read in the GSoC guidelines, we require you to
compile the software and
Hi devansh,
We manage the GSoC-ers in a dedicated mailing-list 'g...@lists.scilab.org'.
Please repost to this
ML.
Thanks,
--
Clément
Le mercredi 02 mars 2016 à 23:28 +0530, Devansh Gohil a écrit :
> Respected Sir,
>
> I am a B.Tech second year student of Information and
ug report number is
> it?
> Thanks
> Wolfgang
>
>
> > -Ursprüngliche Nachricht-
> > Von: users [mailto:users-boun...@lists.scilab.org] Im Auftrag von Clément
> > David
> > Gesendet: Mittwoch, 24. Februar 2016 17:06
> > An: users@lists.scilab.org
>
Hi Samuel,
Le mercredi 24 février 2016 à 15:27 +0100, Samuel Gougeon a écrit :
> I am pretty sure that an horizontal iterator was recently implemented for the
> format
> used within mprintf(), but i am failing to find any information about how to
> use it.
What do you mean by "horizontal
Hi Antoine,
Note sure about that, we have to investigate more on that point and opening two
bug will leave the
door open to solving issues in two ways.
--
Clément
Le mardi 23 février 2016 à 18:27 +0100, Antoine Monmayrant a écrit :
>
> Le Mardi 23 Février 2016 17:16 CET, Clément
Hi Wolfgang,
It seems to be a bug, please report it.
--
Clément
Le mardi 23 février 2016 à 14:48 +, SCHULZ Wolfgang a écrit :
> Hello,
> since Scilab 6.0 beta 1 I have a problem with the input function (everything
> worked under Scilab
> 6.0 alpha 1).
>
> I execute the following code:
>
Hi Simon,
Thanks for answering yourself :)
about the port sizes prompting for MUX / DEMUX you can enforce the size on
parameters using a vector
notation `[1 1 1]` instead of `3`.
--
Clément
Le mardi 16 février 2016 à 06:04 -0700, simon_46_scilab a écrit :
> Ok, I have solved the problem
Hello guys,
Just a pointer there : about the stacksize re-introduction or not please
comment on http://bugzilla.
scilab.org/show_bug.cgi?id=14266 .
--
Clément
Le mardi 16 février 2016 à 13:12 +0100, Antoine Monmayrant a écrit :
> Le 02/16/2016 01:00 PM, Jan Åge Langeland a écrit :
> > On
Hi Antoine,
In fact this module is only available for windows x86 or x64 with Scilab 5.5.2
installed. I just
checked and it is not available on Scilab 5.5.0.
You have to enforce the installation by downloading the zip file and using
`atomsInstall('visa.zip')` directly.
--
Clément
Le mardi 16
Hello all,
Yes, that's quiet strange results and we probably have a bug on that
expression. Could you open a
bug to track that issue please ?
But more generally, on the Scilab5 vs Scilab6 performance, we (Calixte in fact)
made some analysis
pass for our JIT demo use-case and we may re-use it
(answered on dev)
Hi Adhitya, please avoid cross-posting on mailing-lists.
See http://mailinglists.scilab.org/Documentation-for-Xcos-td4033357.html
--
Clément
Le samedi 30 janvier 2016 à 11:52 +0530, Adhitya Kamakshidasan a écrit :
> Hi,
>
> My name is Adhitya Kamakshidasan and I'm an Intern
g Scilab modules for examples, maybe I've
> done something wrong.
>
> Thank you for feedback,
>
> David
>
> -Message d'origine-
> De : users [mailto:users-boun...@lists.scilab.org] De la part de Clément David
> Envoyé : jeudi 28 janvier 2016 16:14
> À : use
Hi David,
The nightly build help is not available on help.scilab.org but we can either
type `help debug` on a
nightly build or read the raw XML on the source tree [1].
Note that this debug feature has no integration on SciNotes yet.
[1]:
Hello Benoit,
During code generation, scilab will generate both the C file of the superblock
and the equivalent
block interface function (a scilab macro). To re-use it later, you have to link
the library (to load
the simulation function) and the execute the interface function file (to load
the
Hello Yash,
Thanks for your interest for Scilab and yes we will try to be a mentoring
organisation this year
again.
Note that we use the Gsoc ML to communicate with students and mentors so please
get in touch in that
channel. And also follow the guidelines,
Hello,
This message means that there is an algebraic loop detected by the solver on
the continuous states
(eg. a value that must change but does not) and might be fix by either :
1) finding and fixing them on the diagram (by
2) reducing solver tolerances on the simulation setup
Regards,
--
Hi Umut,
Did you try adding the `scicos_block.dll` file to the VC++ path ? For FMU
generation, we need block
simulation functions thus you need to link against them.
If you find some issues, do not hesitate to report bugs to the forge.
Regards,
--
Clément
Le dimanche 29 novembre 2015 à 17:35
Hello,
Do you use any hierarchy ? If the current `scs_m` level is exported it might be
sufficient in my
view.
Can you open a bug describing your need ? I will try to implement that for
Scilab 6.0.
Regards,
--
Clément
Le jeudi 12 novembre 2015 à 06:45 -0700, Nazreen a écrit :
> Dear Sir,
>
currently provide
no documented way to
achieve that. Can you clarify your needs ? Do you setup the solver on a block ?
What kind of
information do you need ?
--
Clément
Le mercredi 11 novembre 2015 à 19:41 -0700, Nazreen a écrit :
> Dear Mr. Clément David,
>
> I am developing a toolbox with
Hello all,
In fact, we just mapped some Java layout to the UIControls API. To have
nice tutorials on that refers to the Java Layouts [1] tutorials. And
for beginners on UI, I strongly suggests you to use Netbeans Swing GUI
Builder [2] or Eclipse Swing Designer [3] to discover panel placement
Hello,
This seems to be a bug, can you report it on bugzilla.scilab.org ?
Please also provide an example schema and tell us what Scilab version
you are using.
Regards,
--
Clément
Le mardi 20 octobre 2015 à 00:09 +0530, Parthageet Samantaray a écrit :
> Hello Everyone,
>
> I have trying to
Hello,
Well in fact the `evstr` call is not needed if you parse the csv and
interpreting directly the values as "double" using :
M = csvRead('/tmp/sample.csv', ';', "double");
values = M(:,2);
Regards,
--
Clément
Le lundi 12 octobre 2015 à 18:00 +0200, grivet a écrit :
> Thank you Samuel,
echanic). I got myself thinking: if it wasn't a function that
> I already know, or in a complex block I could think the result is
> numerically right, when it's not.
>
> Thanks Anyway.
>
> On Mon, Oct 5, 2015 at 5:08 AM, Clément David <
> clement.da...@scilab-enterp
Hello Umut,
This error seems to be an NMAKE issue. Can you provide us more
information please ? Did you try logging the makefile using
`ilib_verbose(2)` ?
If possible, can you attach the MBLOCK content or the schema ?
Regards,
--
Clément
Le mardi 06 octobre 2015 à 14:57 +0200, Dr.Umut Durak a
Hello eddie,
See http://math2.org/math/integrals/more/restrig.htm
In fact you can move the starting point by changing the '1/s' initial
value (which is by default 0).
Regards,
--
Clément
Le samedi 03 octobre 2015 à 09:49 -0700, eddie Liberato a écrit :
> Hi,
>
> Going straight to the point,
Hello Samuel,
> So, my questions are:
> * can't the same be implemented in Scilab 6?
No it can not be exactly the same as we no more used a stack approach
for Scilab 6.
> * If yes: is there a way to implement it in such a way that sharing
> between global and local+intermediate
Le mercredi 30 septembre 2015 à 16:04 +0200, Samuel Gougeon a écrit :
> The meaning of my first post was that, from a user point of view,
> knowing that the amount of memory involved in a Scilab session is of
> "Scilab global kind" or of "Scilab intermediate kind" or of "java
> kind"
> or of
Hello,
To handle a cross-platform sound handling in Scilab I suggest you to
take a look at JIMS and the "Java Sound API". Not sure if it will fit
your needs but might be.
Note: another more advanced approach is to use SWIG-Scilab to generate
the mapping of a library (Gstreamer might be a good
101 - 200 of 263 matches
Mail list logo
