Refactor to get threaded operations when writing *.tptp and *.tff KBs #164
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 30 commits
February 11, 2025 17:12
capability of main method
However, this will produce interleaved metadata (documentation), but speeds up processing by a factor of 2. With no (-R), then orig. sequential processing with ordered metadata
shutdown so that we don't have to manually do this
ops, and default unsynchronized.
for threaded ops, and default unsynchronized.
documentation before submitting to the PrintWriter. Keeps order during threaded ops
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
About a week and a half's work. Have tested every which way I can think of, but it finally works. However, there is an issue with writing out to *.tff. TinySUMO writes out identically to pre-threaded sequential form. Top Only has an issue as exposed by Vampire and LEO checking, but this issue existed before this work (verified by checking from previous commits before stating the threaded work).