<
From version < 23.1 >
edited by Isak Björhag
on 2019/05/13 15:53
To version < 24.1 >
edited by Iwona Budny Bjergø
on 2019/05/14 13:13
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.isakbjorhag
1 +xwiki:XWiki.IwonaBudny
Content
... ... @@ -2,7 +2,7 @@
2 2  (((
3 3  **Contents**
4 4  
5 -{{toc depth="4" start="2"/}}
5 +{{toc depth="3"/}}
6 6  )))
7 7  
8 8  More about FEM-Design API
... ... @@ -13,42 +13,61 @@
13 13  
14 14  ----
15 15  
16 -== Introduction ==
16 += Introduction =
17 17  
18 +
19 +(% style="text-align: justify;" %)
18 18  This is an introduction to the FEM-Design API functionality. The program is accessed by different XML files which can be generated from scratch, modified or used as a template. This can be done in many different ways and with many different programming languages. This makes the API functionality in FEM-Design very versatile. The following examples on this wiki is done in python but the same work flow can be used together with VB, C++ or other common languages.
19 19  
22 +
20 20  {{video ratio="16:9" url="https://youtu.be/A4NZuiVovQg" height="200" width="50"/}}
21 21  
22 -XML is a common markup language that is used to store and transport data. The file format uses different elements in a hierarchy, much like HTLM. The different elements is found inside the tag for example ##<entities>##. The element can have other elements below it in the hierarchy. These elements further describes the content of the element. For example the ##<bar>## element contains ##<bar_part>## which in turn contains the ##<curve>## element which defines the geometry of the bar. The start of the element is defined with the name between tags: ##<bar>.## The end of the element is defined with a slash in front of the name: ##</bar>##
23 23  
24 -The top element is called the root element, in the example below it is the ##<database>## element (marked in red). The elements below the database element is called child elements, for example the ##<entities>## element (marked in green). The ##<bar>## element (marked in blue) is a child to ##<entities>## and thus a grand child to the ##<database>## element, and so on.
26 +(% style="text-align: justify;" %)
27 +XML is a common markup language that is used to store and transport data. The file format uses different elements in a hierarchy, much like HTLM. The different elements is found inside the tag for example <entities>. The element can have other elements below it in the hierarchy. These elements further describes the content of the element. For example the <bar> element contains <bar_part> which in turn contains the <curve> element which defines the geometry of the bar. The start of the element is defined with the name between tags: <bar>. The end of the element is defined with a slash in front of the name: </bar>
25 25  
29 +(% style="text-align: justify;" %)
30 +The top element is called the root element, in the example below it is the <database> element (marked in red). The elements below the database element is called child elements, for example the <entities> element (marked in green). The <bar> element (marked in blue) is a child to <entities> and thus a grand child to the <database> element, and so on.
31 +
32 +
26 26  [[image:1557223235184-585.png||height="271" width="1200"]]
27 27  
28 28  
29 -An element can have an attribute. This information is found inside the tag, an example of this is marked in red in the picture below. It can also have a text value which is found between the tags, example marked in yellow.
36 +(% style="text-align: justify;" %)
37 +An element can have an attribute. This information is found inside the tag, an example of this is marked in red in the picture below. It can also have a text value which is found between the tags, example marked in yellow.
30 30  
39 +
31 31  [[image:1557224680285-333.png||height="158" width="800"]]
32 32  
33 33  
43 +(% style="text-align: justify;" %)
34 34  There are two different types of XML files in FEM-Design, the first is called struxml and contains the objects of the model. The second one is used to execute different types of calculations and to export results. This file type is called fdscript. For more information about the script function, please visit the [[wiki page.>>doc:FEM-Design API.Run script.WebHome]]
35 35  
46 +(% style="text-align: justify;" %)
36 36  FEM-Design is able to both read and export models to struxml file format. Go to "File/Save as..." and choose struxml as the format. Go to "File/Open" to open the struxml file or just drag it into the FEM-Design window.
37 37  
38 38  **<link to struxml Schema>**
39 39  
40 40  
41 -== Customer cases ==
52 += Customer cases =
42 42  
54 +
43 43  Did you use the API functionality in your project? Please contact us with feedback and you may also be featured on the wiki!
44 44  
45 -=== Bridge geometry ===
57 +(% class="wikigeneratedid" %)
58 +=== ===
46 46  
60 +== Bridge geometry ==
61 +
62 +
63 +(% style="text-align: justify;" %)
47 47  The bridge is modeled with shell elements and the geometry is complex with different thickness and angles of the shells. This is almost impossible to modell by hand so instead it is generated with a script. The geometry is defined as a nodal list with different thicknesses.
48 48  
66 +
49 49  [[image:1557491889197-384.png||height="594" width="800"]]
50 50  
51 51  [[image:1557491914708-988.png||height="423" width="1000"]]
52 52  
53 53  
54 -**Customer: Norconsult AS**
72 +(% style="text-align: justify;" %)
73 +Customer: Norconsult AS
Copyright 2020 StruSoft AB
FEM-Design Wiki