Tour automatic generation » History » Version 2
Txinto Vaz, 12/19/2013 04:34 AM
1 | 1 | Txinto Vaz | h1. Automatic generation |
---|---|---|---|
2 | 1 | Txinto Vaz | |
3 | 1 | Txinto Vaz | We have seen that uCANca allows us to specify a system and model its design. But this can be seen as "uCANca let's you feed it". Okay but... what will uCANca do for me? |
4 | 1 | Txinto Vaz | |
5 | 1 | Txinto Vaz | uCANca project has a "roadmap":/projects/ucanca/roadmap to know which things will be able to do for you in the future but, having this future in the scope... what can uCANca give me NOW? |
6 | 1 | Txinto Vaz | |
7 | 1 | Txinto Vaz | * Automatic source code (based on flow types)generation of: |
8 | 1 | Txinto Vaz | ** DRE pool. |
9 | 1 | Txinto Vaz | ** function calls to acquire/synthesize magnitudes. |
10 | 1 | Txinto Vaz | * Automatic FSM generation through "CodeDesigner RAD":http://www.codedesigner.org/ project files. |
11 | 2 | Txinto Vaz | * Automatic "Scilab/XCos":http://www.scilab.org/scilab/gallery/xcos project skeletons including subsystem tree and input/output flows of every subsystem. |
12 | 2 | Txinto Vaz | * Automatic "LabView":http://www.ni.com/labview/esa/ VI project skeletons including input acquisition and output acquisition based on VI control patterns for flow type and direction. |
13 | 1 | Txinto Vaz | |
14 | 1 | Txinto Vaz | We will cover these topics on next chapters. |