First time here? Check out the Help page!
1 | initial version |
After focusing on the *.BDL output files, I started to notice a file fort.22. This looks similar ... I found there was a statement like this halfway through my BDL:
##write
Evidently, I needed to put this at the entry point to my program, ie. the beginning of the INP file. The fort.22 file has a clean version of the BDL output file. Aside from line numbers in the first few columns, I think is exactly what I'm looking for.
2 | No.2 Revision |
After focusing on the *.BDL output files, I started to notice a file fort.22. This looks similar ... I found there was a statement like this halfway through my BDL:
##write
Evidently, I needed to put this at the entry point to my program, ie. the beginning of the INP file. The fort.22 file has a clean version of the BDL output file. Aside from line numbers in the first few columns, I think is exactly what I'm looking for.
On second look: This is still not correct, or perhaps there is a bug with DOEBDL. My BDL output file will show keyword expressions, a la {...}
. However, in the fort.22 output file, these expressions are replaced with just the open curly brace, {
, with no inner content. I also get snippets of library in unexpected places.