[go: up one dir, main page]

Menu

#78 Redo LoggingObserver

0.5 goal
open
nobody
None
nobody
2024-04-01
2017-02-07
Ulf Lorenz
No

The LoggingObserver is currently rather primitive and not tested, but has become sufficiently complex that this should change.

After implementation of Ticket 68, it should be refactored. As one preliminary idea, the LoggingObserver should be split into four classes:

  • A printer that deals with the actual output
  • A calculator that calculates the various expectation values
  • A LoggingObserver that ties the printer and calculator together
  • A factory that sets up everything accordingly

Several use-cases should be kept in mind here:

  • Output should be possible to multiple streams (files and/or stdout/stderr)
  • Proper handling of electronic states (only electronic grid, resolve data for each electronic state, handling of multiple electronic grids (?)), also note that the current implementation takes only one Hamiltonian.
  • Proper handling of multiple coupled equations of motion (Redfield equations)

Related

Tickets: #68

Discussion

  • Ulf Lorenz

    Ulf Lorenz - 2017-02-07
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -10,3 +10,4 @@
     Several use-cases should be kept in mind here:
     * Output should be possible to multiple streams (files and/or stdout/stderr)
     * Proper handling of electronic states (only electronic grid, resolve data for each electronic state, handling of multiple electronic grids (?))
    +* Proper handling of multiple coupled equations of motion (Redfield equations)
    
     
  • Ulf Lorenz

    Ulf Lorenz - 2017-06-25
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,13 +1,14 @@
     The LoggingObserver is currently rather primitive and not tested, but has become sufficiently complex that this should change.
    
    -After implementation of [#68](Ticket 68), it should be refactored with this in mind. Preliminary idea:
    -* Split the LoggingObserver into four classes:
    -    * A printer that outputs everything given relevant values
    -    * A calculator that calculates the various expectation values
    -    * A LoggingObserver that ties the printer and calculator together
    -    * A factory that sets up everything accordingly
    +After implementation of [Ticket 68](#68), it should be refactored. As one preliminary idea,  the LoggingObserver should be split into four classes:
    +
    +* A printer that deals with the actual output
    +* A calculator that calculates the various expectation values
    +* A LoggingObserver that ties the printer and calculator together
    +* A factory that sets up everything accordingly
    
     Several use-cases should be kept in mind here:
    +
     * Output should be possible to multiple streams (files and/or stdout/stderr)
     * Proper handling of electronic states (only electronic grid, resolve data for each electronic state, handling of multiple electronic grids (?))
     * Proper handling of multiple coupled equations of motion (Redfield equations)
    
     

    Related

    Tickets: #68

  • Ulf Lorenz

    Ulf Lorenz - 2019-02-17
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -10,5 +10,5 @@
     Several use-cases should be kept in mind here:
    
     * Output should be possible to multiple streams (files and/or stdout/stderr)
    -* Proper handling of electronic states (only electronic grid, resolve data for each electronic state, handling of multiple electronic grids (?))
    +* Proper handling of electronic states (only electronic grid, resolve data for each electronic state, handling of multiple electronic grids (?)), also note that the current implementation takes only one Hamiltonian.
     * Proper handling of multiple coupled equations of motion (Redfield equations)
    
     
  • Ulf Lorenz

    Ulf Lorenz - 2020-01-01
    • Milestone: Backlog --> 0.4 goal
     

Log in to post a comment.