From iurcic at gmail.com Sun Jun 1 00:47:22 2014 From: iurcic at gmail.com (Iurie) Date: Sat, 31 May 2014 23:47:22 +0100 Subject: [Scilab-Dev] [Gsoc] SOCIS 2014 In-Reply-To: References: Message-ID: Hi, i would like to implement a new interface for the scilab for the new version of freefem. i have seen here: http://atoms.scilab.org/toolboxes/SciFreeFEM/1.2.1 that u have created/updated that interface, so i think that u are the right person to ask some thinkgs about updating scilab to the new version of freefem. so i have downloaded the freefem and scilab and SciFreeFem 1.3 and i am trying to figure out how that is implemented on the old version. i have surfed among all (freefem and scilab and SciFreeFem 1.3) and i am not able to properly understand the source code so that i could update it to be compatibel with the new version of the freefem. the code is poorly commented so i have some difficulties in understanding it. furthermore i have also downloaded the getfem which already has a interface for the latest freefem and it is also poorly commented so i also have some difficulties to undersant it. so i would like to ask u for help. i thank you in advance for the help best regards On Thu, May 29, 2014 at 11:41 AM, Marek Olejn?k wrote: > Good Day, > > I would like to participate this years SOCIS 2014. I have basic experience > with C/C++ but mainly with Java so I will prioritize some projects with > Java. I would like to work on some project that has priority for you. I > would like to ask you to recommend me project on which I would write > proposal. Thank You. > > I am also sending you CV link ( > https://dl.dropboxusercontent.com/u/15332014/CV.pdf ) > > Regard, > > Marek Olejn?k > > _______________________________________________ > gsoc mailing list > gsoc at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/gsoc > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From masilvabustos at ieee.org Thu Jun 26 03:29:25 2014 From: masilvabustos at ieee.org (=?UTF-8?Q?Mat=C3=ADas_Silva_Bustos?=) Date: Wed, 25 Jun 2014 22:29:25 -0300 Subject: [Scilab-Dev] code generation for microcontroller target Message-ID: Hello, I am about to begin the developement of a coder that takes a xcos diagram and generates C code suitable to be ran on a ARM Cortex M3 uC, a STM32FXXX in particular. Here my questions: a) Is the code generated by the xcos CodeGenerator suitable for this purpose without much code rewritting? a_1) i.e. has the generated code too many library dependencies? I tryed to compile the XXX_standalone.c but it seems to require many scilab libraries, Am I right?. b) Should I begin from scratch? I think I can reuse the xcos parser and some other code involving the diagram description. b_1) But from there, Is there other classes or functions I can use? c) Scilab is the preferred programming language? I have seen many languages such as C, C++, Java, Modelica (i'm not sure what this is), FORTRAN. d) What is the format of the zcos files? Which issues has the xcos (XML)? :( I'm electronic engineer student from Argentina. I was asked to do this project by a professor and I accepted the challenge. Many thanks for considering my request. Sincerely, Mat?as Silva Bustos. -------------- next part -------------- An HTML attachment was scrubbed... URL: From clement.david at scilab-enterprises.com Thu Jun 26 14:32:32 2014 From: clement.david at scilab-enterprises.com (=?ISO-8859-1?Q?Cl=E9ment?= David) Date: Thu, 26 Jun 2014 14:32:32 +0200 Subject: [Scilab-Dev] code generation for microcontroller target In-Reply-To: References: Message-ID: <1403785952.2024.33.camel@paros> Hello Matias, Answered in-line. Le mercredi 25 juin 2014 ? 22:29 -0300, Mat?as Silva Bustos a ?crit : > Hello, > > I am about to begin the developement of a coder that takes a xcos > diagram and generates C code suitable to be ran on a ARM Cortex M3 > uC, a STM32FXXX in particular. Great ! Do you plan to generate an application using a POSIX-like OS ? if not, what's the minimal set of feature of your platform (eg. bare-metal, contiki / Osek like, RTEMS, Embedded Linux, Full Linux) ? > Here my questions: > > > a) Is the code generated by the xcos CodeGenerator suitable for this > purpose without much code rewritting? It is, as it generates the scheduler code (with restriction), generate I/o wrappers functions and calls to the Scilab block. Note that even if huge double buffers are generated, small to medium diagrams might not have any issue to run on your target. > a_1) i.e. has the generated code too many library dependencies? I > tryed to compile the XXX_standalone.c but it seems to require many > scilab libraries, Am I right?. Yes you are, we do *NOT* generate code for each block but re-use the Scilab's one. The code generator is mainly a scheduler code generator. Not that it may depend on your schema, some block functions requires blas/lapack, others scilab graphics and others nothing but libm/stdlib. You have to take care, some blocks are coded in fortran so your embedded platform might have a fortran compiler. > b) Should I begin from scratch? I think I can reuse the xcos parser > and some other code involving the diagram description. In my view, to generate code that perform the same way as the simulator you have to re-use the cpr structure (help scicos_cpr). The better way to kick things off is to start from the current generator and start refactor it (it's a nightmare) / implement some code generator templates per simulation function. Using well design code generator templates will allow you to both reduce the actual generated code size and runtime requirements. > b_1) But from there, Is there other classes or functions I can use? scinotes "SCI/modules/scicos/macros/scicos_scicos/do_compile_superblock42.sci" will let you edit the whole code generator. Do not hesitate to ask if you need more information ; that's a big piece of old Scilab code ! > c) Scilab is the preferred programming language? I have seen many > languages such as C, C++, Java, Modelica (i'm not sure what this is), > FORTRAN. As all Xcos informations are stored as Scilab variables, it might be easier to code using the Scilab language. To use another language you have "convert" the cpr structure to a language-native one. > d) What is the format of the zcos files? Which issues has the xcos > (XML)? :( The Zcos file format is a zip file containing a "content.xml" file. All Scilab data is encoded through javasci in Java encoded arrays in the "dictionary/dictionary.ser" file. Regards, > I'm electronic engineer student from Argentina. I was asked to do this > project by a professor and I accepted the challenge. > > > Many thanks for considering my request. > > Sincerely, > > Mat?as Silva Bustos. > -- Cl?ment DAVID Development Engineer / Account Manager ----------------------------------------------------------- Scilab Enterprises 143bis rue Yves Le Coz - 78000 Versailles, France Mobile: +33.6.26.26.51.90 Phone: +33.2.90.22.78.96 http://www.scilab-enterprises.com