DAE Tools Project Files

                DAE Tools v1.7.2 (30 August 2017, updated 12 September 2017)

Supported platforms: GNU/Linux (x86_64), macOS (x86_64) and Windows (32 and 64 bit).

Binaries provided for GNU/Linux, macOS and Windows (python 2.7, 3.4, 3.5 and 3.6). 

Linux binaries compiled with:
 - g++ 6.3 (libc 2.24)
 - g++ 4.9 (libc 2.19)
Windows binaries compiled with msvc++ 2015.
macOS binaries compiled with g++ 6.3 and XCode 7.3.1.

All platforms use PyQt5.

                                Installation

All platforms (GNU/Linux, macOS, Windows):

  Unpack the archive and run (may require sudo): 
  python setup.py install

                                 Changelog
                            
Release info:
- Windows 64 bit version available.
- Updated support for FMI code-generator.
- Added daeActivity class to handle execution of simulations/optimisations.
- Updated all data reporters.

New features:

- Windows x64 port available. Installation files updated to support it.
- New class daeActivity with two static functions: simulate and optimize.
  Updated all tutorials with the new, simpler way of executing simulations.
- Fixed FMI code generator, SimulationLoader and FMU_CS libraries:
  - Exported FMU files now contain win64 binaries
  - FMU_CS library does not link cdaeConfig shared library anymore
  - Fixed resources['simulationFile'] value in fmi.py 
    (it should be only the filename not the full path).
  - In Windows python/Lib and Python/DLLs directories are programmatically 
    added to the PATH/PYTHONPATH (in the SimulationLoader library).
  - In GNU/Linux Python/lib directory needs to be manually added to the 
    LD_LIBRARY_PATH (only for custom python installations and virtual 
    environments; system python installations do not need this)
  - In GNU/Linux python shared library needs to be loaded using dlopen 
    (despite it was already loaded by FMI_CS library). Otherwise the code
    does not work: for instance, numpy cowardly refuses to import
  - Variables from the top-level model can be exported as 'local' 
    or 'output' FMI variables.
  - All tutorials setup and execute simulation in the run(**kwargs) function. 
    This way, the same simulation setup can be used for co-simulation runs as well.
    daeActivity.simulate function have a new boolean argument initializeAndReturn 
    used for returning an initialised simulation object in co-simulation.
  - Additional files argument of the daeCodeGenerator_FMI.generateSimulation 
    function is now a list of tuples: 
    [('file_path', 'resources_dir_relative_path'), ...]
    i.e. in tutorial_dealii_1: [(mesh_file, 'meshes/step-49.msh')]
  - Added a new optional argument to the daeCodeGenerator_FMI.generateSimulation 
    function: localsAsOutputs = False. If it is true, variables from the
    top-level model are added as output FMI variables; otherwise, they
    are added as local FMI variables.
  - Function daeModel::GetCoSimulationInterface now has a new argument
    std::vector<daeVariable_t*>&  ptrarrModelVariables filled with the 
    variables from the top-level model (treated as locals in FMI).
  - Function daeModel::GetFMIInterface now also adds variables from the 
    top-level model to the std::map<size_t, daeFMI2Object_t> map as
    FMI 'Local' variables.
  - Function daeSimulationLoader::GetFMIValue now also returns values
    for 'Local' FMI variables.
  - Fixed bug in getFolderFromURI function (handling of file:/// in Windows).
  - Added a new function: daeSimulationLoader::SetRelativeTolerance.
    It is used in the fmi2SetupExperiment function to handle the tolerance
    argument (if toleranceDefined argument is true). 
  - Updated generate_fmus.py file. It generates the FMU files for selected
    tutorials and generates all files required for the FMI ComplianceChecker
    (i.e. scripts to run .fmu files with the ComplianceChecker, the reference 
    solution from the exporting tool, the .opt options and ReadMe.txt files).
  - DOFs (assigned variables) are now added as FMI inputs
  - FMU_CS does not set the time horizon nor does reinitialization before every 
    time step (in fmi2DoStep function)
  - FMU modeDescription.xml file can have an optional xml-stylesheet added 
    (daetools-fmi.xsl)
- Intel Pardiso solver available on win32, win64 and GNU/Linux x86_64
- SALib and pyevtk included with daetools (in ext_libs module).
- Updated all data reporters. All export file data reporters export 
  Units, DomainNames, Domains, Times and Values for all variables. 
  daeExcelFileDataReporter uses openpyxl used instead of xlwt library.
- setup.py now used setuptools (not distutils).
- daeexamples and daeplotter now use i.e. python -m daetools.dae_plotter.plotter 
  instead of longer python -c "..." commands.
- Mumps and Bonmin can be compiled from the command line in Windows.
  gfortran from mingw32/mingw64 used for compiling mumps.
- Python wrappers now keep the references to the python objects: 
  - simulation -> stores daesolver, datareporter and log
  - idas -> stores lasolver
  - delegate data reporter -> stores added data reporters
  - optimization -> stores simulation
  This way, the python wrappers take the responsibility from modellers for keeping 
  the objects (they will not get destroyed when they go out of scope causing the 
  segmentation fault).
- daetools.cfg config file is now properly located on all platforms.
- New daeSimulation properties: StopAtModelDiscontinuity and 
  ReportDataAroundDiscontinuities and new boolean options stopAtModelDiscontinuity 
  and reportDataAroundDiscontinuities in daetools.activity section n daetools.cfg.
  The properties control the default behaviour of daeSimulation.Run function.
  If StopAtModelDiscontinuity=true the simulation will stop at every discontinuty. 
  If ReportDataAroundDiscontinuities=true the data will be reported before and 
  after the discontinuity.
- Added a new daeCSVFileDataReporter (saves the results into a .csv file).
- OpenMP assembly refactored into the OpenMP_WorkStream::run function.
- Added OpenMP shared library (vcomp.dll) to the setup.py in Windows.
- Fixed bug in daeVariable::GetType function.