Alternative simulatiom method: Independent translation from simulation

[mrosemeier]

The translation time of relatively large models can be significant. If lots of cases of such large models are simulated it makes sense to translate the model only once and simulate it with varied parameters (if the model allows to vary parameters after translation).
For this purpose I have added two methods:

• translate()
• simulate_translated()

which can be executed consecutively. Each method executes Dymola once. An example (runSimulationTranslated.py) is also added showing how to benefit from this alternative method.

Basically the workflow looks as follows:

• Create a Simulate object.
• Set arbitrary model parameters, modifiers, and simulation settings.
• Translate the model (while keeping the temporary translate folder in mind).
• Deepcopy the Simulate object as many times as wished.
• Set arbitrary model parameters and simulation settings for each copy.
• For each simulation the temporary translate folder is copied.
• Run simulations in parallel (note that for the simulations a Dymola license is not required).
• Delete the temporary translate folder.

Some notes on fixes:

• Since my Eclipse PyDev IDE did not allow referencing projects without a src folder the same has been added.
• Since I am inheriting from the Simulator object in my project the same needed to inherit from object. http://stackoverflow.com/questions/4015417/python-class-inherits-object

Feel free to comment on my request!

[mwetter]

@mrosemeier : Thanks for the pull request. I merged it to branch issue70_simulation for further development and added the ticket #70 to track further changes and discussions that are needed before putting on the master.

I also changed back the code from BuildingsPy/src/buildingspy to BuildingsPy/buildingspy. It seems not necessary to put it in src (for me PyDev works as it is).

The regression and doctests have been fixed, now make doctest unittest works again.