Tutorial

[home]

Start the FactoryEditor :



Define factory basics Back to top

[manual]
Set factory name and description :

Define used types :


Add action "LoadMesh" Back to top

[manual]
Add the action and set its name and description :

There are no input ports for this action.
Define output ports:

Define parameters:


Add action "WriteMesh" Back to top

Add the action and set its name and description :

Define input ports :

There are no output ports.
Define parameters:


Add action "Solver" Back to top

Add the action and set its name and description :

Define input ports :

Define output ports:

Define parameters:


Save your factory Back to top

[manual]
Save the factory in file "Test.factory.xml".


Start the MapEditor :



Load factory in MapEditor Back to top

[manual]
Switch MapEditor to "Specification" mode, then load your factory descrription from "Test.factory.xml".


Create "LoadMesh", "Solver" and "WriteMesh" action boxes Back to top

[manual]
Create a "LoadMesh" action box, and set it's internal parameters. Set the "Filename" parameter as global shared :

Create a "Solver" action box, and set it's internal parameters :

Create a "WriteMesh" action box. Set the "Filename" parameter as global shared to fix the same Filename value as in LoadMesh :


Create command box Back to top

[manual]
Create a command action box, name it "EditFilename" and set it's internal ordrer to an editor command ('xterm -e vi Filename' should work almost anywhere):


Establish connexions Back to top

[manual]
Connect LoadMesh output port MeshOut to Solver input port MeshIn.
Connect Solver output port MeshOut to WriteMesh input port MeshIn.
Connect WriteMesh output port Trigger to EditFilename input port.

On WriteMesh output port, activate the UseTrigger checkbox.


Run simulation in specification mode, save your map Back to top

[manual]
Switch to "Auto Fire" mode, run your specification and look at the listing to check if it behaves as you wish it should.
Then save your map in "Test.map".


At this stage, the user should give its specification files to the integrator :

  • the "Test.factory.xml" file as a specification file
  • the "Test.map" as a use case file
The user should keep its "Test.map" file, because it'll be directly used for steering the simulation once the integrator will have provided a proper implementation.


Specify servers and generate Back to top

[manual]
Launch the FactoryEditor, load the "Test.factory.xml" factory specification, and complete the "Server" tab of each action notebook with the name of the FactoryObjects (see FactoryACtion documentation) that will be needed to realize the implementation.
For each "LoadMesh", "WriteMesh" and "Solver" action, specify you'll need the "FactoryObjectTest" server :

Save your updated factory description, and generate the C++ wrapper :


You should now switch to the FactoryAction tutorial to complete the implementation of the specified FactoryAction.
Let's assume we're back in user's role, with a finished implementation. Our integrator gave us a FactoryActionTest, and we started it.


Reload your computationnal path in execution mode Back to top

[manual]
Leave MapEditor in "Execution" mode, then load your factory description from the running FactoryActionTest.
Load your saved map "Test.map".


Choose execution platforms Back to top

[manual]
For each of the "LoadMesh", "WriteMesh" and "Solver" action boxes, you'll need to specify the host on which you'll want your simulation to run.
See with your integrator if he's set the automatic activation or not, and act accordingly (see manual).
Save your updated computationnal path in "Test.map".


Run the real simulation Back to top

[manual]
Switch to "Auto Fire" mode, and run your computation !


Comments, bugs, fixes to t_chevalier@libertysurf.fr.


[Home]