Programming scicos blocks
fr - eng

block_type - Scicos block type

Contents

• block_type - Scicos block type
  • Module
  • Description
  • Authors

Module

• Scicos

Description

Scicos has the possibility to handle and to call many different sorts of blocks. Some blocks in Scicos palettes are special and are only used internally by Scicos, such as synchro blocks and the Debug block, but most blocks are regular blocks which the user can get inspired by to construct new blocks. The following table gives the known Scicos block types, and is followed by the report of the type of the computational function with its associated calling sequence by block type.

Type	Description	Function type	Simulator call
-2	Event select block (synchro block).	-	Never called.
-1	If Then Else block (synchro block).	-	Never called.
0	C, Fortran or Scilab block. Calling sequence fixed. Obsolete.	Type 0.	Type 0.
1	C or Fortran block. Varying calling sequence. Obsolete.	Type 1.	Type 1.
2	C block. Calling sequence fixed. Obsolete.	Type 2.	Type 2.
3	Scilab block. Calling sequence fixed. Used but obsolete.	Type 3.	Type 2.
4	C block. Calling sequence fixed. In use.	Type 4.	Type 4.
5	Scilab block. Calling sequence fixed. In use.	Type 5.	Type 4.
1001	Fortran block. Dynamically linked. Obsolete.	Type 1.	Type 1.
2001	C block. Dynamically linked. Obsolete.	Type 1.	Type 1.
2004	C block. Dynamically linked. In use.	Type 4.	Type 4.
10001	Implicit C or Fortran block. Obsolete.	Type 10001.	Type 10001.
10002	Implicit C block. Obsolete.	Type 10002.	Type 10002.
10004	Implicit C block. In use.	Type 10004.	Type 4.
10005	Implicit Scilab block. In use.	Type 10005.	Type 4.
30004	Generic Modelica block. Dynamically linked. In use.	Type 10004.	Type 4.
99	Debug block.	Type 5.	Type 4.

Note that even if type 0, 1 and 2 are obsolete, they are still supported in Scicos; some blocks in the standard palettes of Scicos are still of these types. Block type 3 is still used by scifunc block (Scilab block) but users should prefer the type 5 when constructing a computational function in Scilab because it takes full advantage of new data structures. In fact it has all the the functionalities implemented for block type 4.

• Calling sequence of computational function type 0
  void myfun(flag,nevrt,t,xd,x,nx,z,nz,tvec,ntvec,rpar,nrpar,ipar,nipar,u,nu,y,ny)
• Calling sequence of computational function type 1
  void myfun(flag,nevrt,t,xd,x,nx,z,nz,tvec,ntvec,rpar,nrpar,ipar,nipar,u1,nu1,u2,nu2,...,y1,ny1,y2,ny2,...)
• Calling sequence of computational function type 10001 (type 1 implicit)
  void myfun(flag,nevrt,t,res,xd,x,nx,z,nz,tvec,ntvec,rpar,nrpar,ipar,nipar,u1,nu1,u2,nu2,...,y1,ny1,y2,ny2,...)
• Calling sequence of computational function type 2
  void myfun(flag,nevrt,t,xd,x,nx,z,nz,tvec,ntvec,rpar,nrpar,ipar,nipar,inptr,insz,nin,outptr,outsz,nout)
• Calling sequence of computational function type 2 (zero crossing)
  void myfun(flag,nevrt,t,xd,x,nx,z,nz,tvec,ntvec,rpar,nrpar,ipar,nipar,inptr,insz,nin,outptr,outsz,nout,g,ng)
• Calling sequence of computational function type 10002 (type 2 implicit)
  void myfun(flag,nevrt,t,res,xd,x,nx,z,nz,tvec,ntvec,rpar,nrpar,ipar,nipar,inptr,insz,nin,outptr,outsz,nout)
• Calling sequence of computational function type 10002 (type 2 implicit with zero crossing)
  void myfun(flag,nevrt,t,res,xd,x,nx,z,nz,tvec,ntvec,rpar,nrpar,ipar,nipar,inptr,insz,nin,outptr,outsz,nout,g,ng)
• Calling sequence of computational function type 3
  [x,y,z,tvec,xd]=myfun(flag,nevprt,t,x,z,rpar,ipar,u)
• Calling sequence of computational function type 4
  void myfun(scicos_block *block,int flag)
• Calling sequence of computational function type 5
  [block]=myfun(block,flag)

Authors

Alan Layec INRIA