Obsolete parsing and File not found fix #264
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix for #4
The problem is that the obsolete.dat is parsed, but old references are not replaced by newer ones.
I pulled the obsolete last week and still got 'file not found' errors. I could trace it back to the file itself. I added code after parsing, which replaces all cross-references with the latest pdb-ids, replacing all older ones. An example can be shown in the following table:
If you had 6L2V as input, it currently searches for 7BYZ and throws an error and stops.
In the new version, 6L2V gets replaced with 7DE5 and it works flawlessly.