|
| 1 | +About |
| 2 | +============ |
| 3 | +The (original) aim of Pypact was to make the FISPACT-II output file easy to parse so that more time can be spent on analysis, |
| 4 | +and much less time on interrogating the output file. No more convoluted scripts, just one simple to use package! |
| 5 | + |
| 6 | +The FISPACT-II output file is designed to be human readible but not computer readible, therefore it can be quite cumbersome to parse. |
| 7 | +The standard .out file has no strict format, it is not XML, JSON, or CSV it is FISPACT-II custom format. Note since version 4 of FISPACT-II |
| 8 | +there is now a JSON format to make it easier to parse (this was part of the reason pypact exists - to test the JSON output). |
| 9 | + |
| 10 | +A typical output file from FISPACT-II will look something like below: |
| 11 | + |
| 12 | +.. image:: assets/about_file_example.png |
| 13 | + |
| 14 | + |
| 15 | +Over time we have seen many different people implement FISPACT-II output parsers in many different languages, some which are quite extensive, |
| 16 | +with others designed to extract a few values from the output file. All, however, have never fully supported FISPACT-II features and are also |
| 17 | +not open source. Enter pypact. Pypact is: |
| 18 | + |
| 19 | +* open source |
| 20 | +* supported by FISPACT-II developers |
| 21 | +* well tested & validated |
| 22 | +* easy to install & minimal dependencies |
| 23 | +* python (this may be a pro or con depending on who you are) |
| 24 | + |
| 25 | +The last point can of course be a problem for non python enthusiasts, and in that case |
| 26 | +pypact cannot help you. However, from our experience many users of FISPACT-II like to use |
| 27 | +python (very subjective). |
| 28 | + |
| 29 | +Of course with an API in development parsing the output file could be a thing of the past (I hope!), however it will always be needed to write |
| 30 | +file and manipulate them! |
0 commit comments