Date: Fri, 29 Mar 2024 17:01:26 +0700 (NOVT) Message-ID: <431964215.89090.1711706486583@ugene.net> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_89089_305900842.1711706486583" ------=_Part_89089_305900842.1711706486583 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Each elem= ent used in the workflow must be described inside the body.An element description consists of= the element name and a set of parameters enclosed in curly braces. A param= eter and the value are separated by =E2=80=98:=E2=80=99, different paramete= rs are separated by =E2=80=98;=E2=80=99:
element_= name { parameter1:value1; parameter2:value2; ... }=20
See, for example, a description of the Read alignment&nb= sp;element:
read-msa= { type:read-msa; name:"Read alignment"; url-in:/home/user/pkinase.sto; }=20
Note, that the values of the parameters for an element= can also be presented in the i= terations block.For all elements the following parameters are= defined:
For ex= ample this validator validate that the read sequence element has two or thr= ee datasets:
read= -sequence { type:read-sequence; name:"Read Sequence"; .validator { type:datasets-count; min:2; max:3; } }=20
For cus= tom elements there is special parameter:
dump-inf= o { type:"Script-Dump sequence info" name:"Dump sequence info" script { out_text=3DgetName(in_sequence) + ": " + size(in_sequence); } }=20
The list of parameters available depend on an element.= Refer to the Wo= rkflow Elements chapter to find out the parameters for a part= icular element.To set a script value for a parameter use th= e following form:
paramete= r_name { a script value };=20