refactor narsese module #93
Closed
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
|
dev.txt - DEV BRANCH: FAILED (errors=10) |
|
Just found that there are some conflicts with other branches. |
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.
I move
Config.py,Global.py, andconfig.jsonintoNarsesesubmodule, so that one can useNarsesewithout depending onpynars.The demo of
Narsesemodule can be run bypython -m Narsese.demo(suppose the root directory is
./pynars)It should be noted that the current treatment is tentative. For example, all configurable parameters lie in
./pynars/Narsese/Config.py, but maybe it is more suitable to make Narsese related parameters to be there, and move NAL and NARS related parameters into./pynars/Config.py. The same thing for./pynars/Narsese/config.json