1. 20 Mar, 2017 2 commits
  2. 19 Mar, 2017 2 commits
  3. 18 Mar, 2017 5 commits
  4. 17 Mar, 2017 14 commits
  5. 16 Mar, 2017 3 commits
  6. 15 Mar, 2017 3 commits
  7. 13 Mar, 2017 3 commits
  8. 12 Mar, 2017 1 commit
  9. 11 Mar, 2017 1 commit
  10. 10 Mar, 2017 1 commit
    • gsell's avatar
      Merge branch 'BetterErrorMessages' into 'master' · 5a81a8e8
      gsell authored
      First proposition for better error messages
      
      With this patch the user gets a hint about what is wrong in his input file as requested in #32 
      
      If one omits the TRACK command OPAL writes
      ```
      Error>     RUN,METHOD="PARALLEL-T",BEAM=BEAM1,FIELDSOLVER=FS1,DISTRIBUTION=DIST1;
      Error>     Syntax error, the command 'RUN' could belong to
      Error>       - the command TRACK
      Error>     but it's not present!
      ```
      
      If parts of a definition are commented out then OPAL writes
      ```
      Error>     MAXSTEPS=600000,DT=2e-13,ZSTOP=0.3;
      Error>             ^
      Error>     Syntax error, either the keyword REAL is missing or
      Error>     the attribute 'MAXSTEPS' could belong to
      Error>       - the command TRACK
      Error>     but it's not present!
      ```
      
      Disadvantage: one has always to use REAL when defining variables. e.g.
      ```
      MINSTEPFORREBIN = 500;
      ```
      isn't accepted any more. Instead one has to write
      ```
      REAL MINSTEPFORREBIN = 500;
      ```
      
      See merge request !9
      5a81a8e8
  11. 08 Mar, 2017 1 commit
  12. 07 Mar, 2017 4 commits