cbrunet / fibermodes Goto Github PK

• Because it seems PySide is almost abandoned
• Because PyQt is included in anaconda and WinPython (but PySide is not)

It will allow to use Python 3.5 on Windows, and will ease the transition to PyQt5 (when available on Windows)

When a parallel simulation is interrupted, child processes are not killed, and continue to run, even if parent process no longer is running.

Something similar to this:

cutoffs = sim.cutoff()
neffs = sim.neffs()

for f in fibers:
    next(cutoffs)
    next(neffs)

causes deadlock.

The Simulator should be able to perform periodic checkpoints, to resume simulation after a crash or after a user interruption.

Related to #11 .

The SImulator should be able to save its state, and to restore it later. It would allow to continue from a previous simulation, without calculating everything again.

All test files should be names test_*.py. This way nosetests works out-of-the-box and we will be able to perform code coverage.

For instance, if a three-layer fiber becomes a two-layer fiber fiber at some point, plot of the layer boundaries becomes confused.

Proposed solution:

• add a dict in fiber object to keep track of old layer index -> new layer index. This dict is built by the Factory when creating the fibers
• add an optional argument to fiber functions to allow the use of original layer indexing

We should provide an install script for the API. That would simplify PYTHONPATH handling.

Should cover:

• SSIF (cutoff and neff)
• 3LSIF (cutoff and neff)
• multilayer fibers (neff)

Actually, caching is performed, partly in Fiber and partly in Simulator objects. There should be a mechanism for caching computed values, separated from Fiber and Simulator classes. This would simplify Fiber and Simulator classes.

The cache object should be fast and efficient. It should be easy to share cached values among different processes or threads, and even across network.

Installation instructions, for Linux, Windows, and Mac OS, should be provided in the Readme.md file. This should include required dependencies, etc.

See http://johnnado.com/pyqt-qtest-example/

In modesolverapp.py and in fibereditorapp.py, allow to start with a given filename. This will allow the integration with to OS to start the simulator when double-clicking a .solver file.

Provide an output window to display warnings and errors. Redirect stderr and stdout to it. Allow to filter what is displayed. Allow to save output in a text file. Window is hidden by default. Show / hide from debug menu. Save output in a tmp file, to keep it in case of crash. Print file location in case of crash.