From stephane.mottelet at utc.fr Mon Nov 6 17:47:05 2017 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Mon, 6 Nov 2017 17:47:05 +0100 Subject: [Scilab-Dev] Scilab forge down Message-ID: <777ef811-ecc2-68cc-76c3-8de2b0d8915c@utc.fr> Hello Scilab/ESI guys, The scilab forge (forge.scilab.org) seems to be down. Is there a maintenance happening ? I hope that this is just temporary : in the future that would be nice to announce in adavance such unavailabilities... S. From ishafiul at gmail.com Mon Nov 6 21:36:58 2017 From: ishafiul at gmail.com (Shafiul Azam) Date: Mon, 6 Nov 2017 14:36:58 -0600 Subject: [Scilab-Dev] Xcos blocks source code Message-ID: Hello, I'm a new user interested in analyzing xcos source code. I think the xcos source is located in `\scilab-6.0.0\modules\xcos\src\java\org\scilab\modules\xcos` location - is this correct? Next, I'd like to know where code *for simulating* various "blocks" are located. By blocks I mean the individual blocks inside various pallets. For example, where would I find the code for various blocks for the "Sink" or "Source" block-groups? By code, I mean the one which will be used to simulate the model, not Scilab UI code. Thanks! Shafiul -------------- next part -------------- An HTML attachment was scrubbed... URL: From antoine.elias at scilab-enterprises.com Tue Nov 7 09:50:07 2017 From: antoine.elias at scilab-enterprises.com (Antoine ELIAS) Date: Tue, 7 Nov 2017 09:50:07 +0100 Subject: [Scilab-Dev] Scilab forge down In-Reply-To: <777ef811-ecc2-68cc-76c3-8de2b0d8915c@utc.fr> References: <777ef811-ecc2-68cc-76c3-8de2b0d8915c@utc.fr> Message-ID: <58a83d8b-7a56-ffcb-b482-c4b09ed670da@scilab-enterprises.com> Hello all, Since Tuesday evening, services around xxx.scilab.org are interrupted by a hardware failure of an internal connection. ISP is working on it. In the meantime, ITs start to move servers ( VM ) to another site. They started by the mailing list server. I do not have more information except that it is not voluntary. And that ESI IT teams work to solve the problem. Regards, Antoine Le 06/11/2017 ? 17:47, St?phane Mottelet a ?crit?: > Hello Scilab/ESI guys, > > The scilab forge (forge.scilab.org) seems to be down. Is there a > maintenance happening ? I hope that this is just temporary : in the > future that would be nice to announce in adavance such > unavailabilities... > > S. > > > _______________________________________________ > dev mailing list > dev at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/dev From sgougeon at free.fr Tue Nov 7 13:54:05 2017 From: sgougeon at free.fr (sgougeon at free.fr) Date: Tue, 7 Nov 2017 13:54:05 +0100 (CET) Subject: [Scilab-Dev] Xcos blocks source code In-Reply-To: Message-ID: <1791922919.327413234.1510059245530.JavaMail.root@zimbra75-e12.priv.proxad.net> Hello Shafiul, >Hello, > >I'm a new user interested in analyzing xcos source code. >I think the xcos source is located in `\scilab-6.0.0\modules\xcos\src\java\org\scilab\modules\xcos` >location - is this correct? Yes, but as well in the modules SCI\modules\scicos and SCI\modules\scicos_blocks >Next, I'd like to know where code *for simulating* various "blocks" are located. >By blocks I mean the individual blocks inside various pallets. >For example, where would I find the code for various blocks for the "Sink" or "Source" block-groups? >By code, I mean the one which will be used to simulate the model, not Scilab UI code. They are defined in the scicos_blocks module. Scicos is the former name of Xcos, before Scilab was forked in Scicoslab and Scilab. HTH Samuel From ishafiul at gmail.com Tue Nov 7 15:42:54 2017 From: ishafiul at gmail.com (Shafiul) Date: Tue, 7 Nov 2017 07:42:54 -0700 (MST) Subject: [Scilab-Dev] Xcos blocks source code In-Reply-To: <1791922919.327413234.1510059245530.JavaMail.root@zimbra75-e12.priv.proxad.net> References: <1791922919.327413234.1510059245530.JavaMail.root@zimbra75-e12.priv.proxad.net> Message-ID: <1510065774990-0.post@n3.nabble.com> Thanks! Looking at the "modules\scicos_blocks\src\c" directory, it seems to me that most (if not all) blocks are implemented in C code. Is this correct? For a simulation, does Scialb/xcos calls these C code/generates binaries and call them directly? It'd be really great if you could point me to developer documentation to understand how parts of xcos/Scilab is implemented, if such documentations/tutorials exist. Thanks again! Shafiul -- Sent from: http://mailinglists.scilab.org/Scilab-developers-Mailing-Lists-Archives-f2574944.html From hacker at stoerk-tronic.com Wed Nov 8 12:14:54 2017 From: hacker at stoerk-tronic.com (Sebastian Hacker) Date: Wed, 8 Nov 2017 12:14:54 +0100 Subject: [Scilab-Dev] Xcos blocks source code In-Reply-To: References: Message-ID: <2cc765ae-d4ac-5f81-dca1-2cc30df6b8cd@stoerk-tronic.com> Hello, The simulation is defined the the file called "BLOCKNAME.sci" In most cases (esp. for the built in ones) this links to the "BLOCKNAME.c" file. But in Scilab installation folder /contrib/ are 2 toolbox skeletons, that also contain the stuff cut down to the essentials. And: http://www.scicos.org/documentations.html Creating blocks there is really difficult. Stick exactly to the recipe provided by the skeletons, and don't forget to build for new blocks. After that, load the toolbox. The underlying functions can be updated in Scilab memory by executing the definition file, after the toolbox is loaded for quick test iterations (of course, the built package won't be updated). Sincerely, Sebastian Hacker From ishafiul at gmail.com Fri Nov 10 16:11:31 2017 From: ishafiul at gmail.com (Shafiul) Date: Fri, 10 Nov 2017 08:11:31 -0700 (MST) Subject: [Scilab-Dev] Xcos blocks source code In-Reply-To: <2cc765ae-d4ac-5f81-dca1-2cc30df6b8cd@stoerk-tronic.com> References: <2cc765ae-d4ac-5f81-dca1-2cc30df6b8cd@stoerk-tronic.com> Message-ID: <1510326691358-0.post@n3.nabble.com> Thanks a lot! I could not load the website linked. Can you please tell where are the BLOCKNAME.sci files located for the built-in blocks? I could only find the .c files in the modules\scicos_blocks\src\c directory. Concretely, I'm interested in the formal semantics of the blocks, if they're available. If they're not available, I'd like to analyze the blocks' source code, to (automatically) find pre/post conditions for the blocks, for instance. If you're already doing this, or aware of any such work, it'd be great if you could point me to it! Thanks again. Shafiul -- Sent from: http://mailinglists.scilab.org/Scilab-developers-Mailing-Lists-Archives-f2574944.html From hacker at stoerk-tronic.com Mon Nov 13 07:30:48 2017 From: hacker at stoerk-tronic.com (Sebastian Hacker) Date: Mon, 13 Nov 2017 07:30:48 +0100 Subject: [Scilab-Dev] Xcos blocks source code Message-ID: <87860d8c-b85d-ae36-d6c0-7cc7a968a42d@stoerk-tronic.com> Hello, The directly called code for every module is in the macros subfolder of the module. Also stated in the Help. As for mnotation, These Macros return siome scicos block, that containd everything. Insiode you get the required model with scicos_model, which contains all the Executables, parameters, IO sizes,... for the block. The build in bloxks/askeleton shows easily enough, what you need there. Just keep stuff consistent. And that Link worked for me. I checked it before sending it. Sincerely, Sebastian Hacker