revisions after reviews #25
Open
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
related work: added new section (w/ several new references) on background + timeline on other mesh-based visualization tools that leverage python why python for VisIt?: added brief info on the reasons python was selected for scripting by the VisIt team in 2001 client interface API details: details about VisIt’s C++ RPC infrastructure and why the client API is procedural / modal general: fixed some grammar issues, simplified verbiage in a few sections, used the abbreviation “CLI” more consistently
This was referenced Jul 3, 2014
|
Thanks @cyrush - this looks good. |
|
@cyrush I will have a look at it today. |
|
Thanks @aashish24! |
|
I had a quick look. As I said, I was already comfortable with the paper, and these changes are an improvement! So, to be clear, I'm happy to sign off. |
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.
Hello SciPy 2012 Program Committee Members,
I made several improvements based on the reviewers’ suggestions, including:
related work: added new section (w/ several new references) on background + timeline on other mesh-based visualization tools that leverage python
why python for VisIt?: added brief info on the reasons python was selected for scripting by the VisIt team in 2001
client interface API details: details about VisIt’s C++ RPC infrastructure and why the client API is procedural / modal
general: fixed some grammar issues, simplified verbiage in a few sections, used the abbreviation “CLI” more consistently
-Cyrus