Fix the bug when adding new matter #18
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
…he laplace operator
* Update paper.md
* Update paper.bib * Update paper.md
* Create draft-pdf.yml * Update draft-pdf.yml
66a8ab6 to
ce34fc7
Compare
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.
The code breaks when adding new matter in Source/Matter.
To solve this bug, each matter type should be inside its own subdirectory. Therefore
Source/Matter/ScalarFieldhas been added. The path to a specific matter type has to be specified inGNUmakefilefor each example.These changes make it easier and cleaner to add new matter to
Sourceand the use in each example.