Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create user variables for easier output. #30

Merged
merged 13 commits into from Mar 7, 2019

Conversation

Projects
None yet
3 participants
@greebie
Copy link
Collaborator

greebie commented Mar 6, 2019

I pulled out the user variables to make changing the visualization both a little more flexible and easier to see.

Some conventions:

  • I used namespaces DOMAIN_, TEXT_, OVERALL_ and NETWORK_
  • In some cases I used an override DOMAIN_ if (DOMAIN_) else CONFIG_
  • user vars should follow the CAPS_PLUS_UNDERSCORE format.

In some cases, additional descriptions were added to show what's going on a bit better.

@greebie

This comment has been minimized.

Copy link
Collaborator Author

greebie commented Mar 6, 2019

Made the changes in docker and they did not carry over. Going to have to redo it. :(

@ruebot

This comment has been minimized.

Copy link
Member

ruebot commented Mar 6, 2019

@greebie Docker is READ ONLY unless you setup your filesystem mount so that it isn't. Best to do the edits locally.

@greebie

This comment has been minimized.

Copy link
Collaborator Author

greebie commented Mar 6, 2019

Thanks, yeah - I got lazy because I didn't have nltk.stopwords installed. I managed to port my work over from the read only version, fortunately.

I thought I could get away with trying to download the file, but no go.

@@ -752,7 +855,7 @@
"name": "python",
"nbconvert_exporter": "python",
"pygments_lexer": "ipython3",
"version": "3.7.1"
"version": "3.7.0"

This comment has been minimized.

@greebie

greebie Mar 6, 2019

Author Collaborator

This is going to keep changing as different people have their hands on it. Not sure what to do here.

This comment has been minimized.

@ruebot

ruebot Mar 6, 2019

Member

It's fine.

@ianmilligan1
Copy link
Member

ianmilligan1 left a comment

Looks great, and runs well. My comments here are all variations on a theme, just providing more context around the variables.

I also caught one variable error.

Show resolved Hide resolved auk-notebook.ipynb
Show resolved Hide resolved auk-notebook.ipynb Outdated
Show resolved Hide resolved auk-notebook.ipynb
Show resolved Hide resolved auk-notebook.ipynb
Show resolved Hide resolved auk-notebook.ipynb Outdated
Show resolved Hide resolved auk-notebook.ipynb Outdated
Show resolved Hide resolved auk-notebook.ipynb Outdated
Show resolved Hide resolved auk-notebook.ipynb
@ianmilligan1

This comment has been minimized.

Copy link
Member

ianmilligan1 commented Mar 7, 2019

Let me know when you're ready for me to review again @greebie! Looking forward to checking it out.

@greebie

This comment has been minimized.

Copy link
Collaborator Author

greebie commented Mar 7, 2019

One more tiny fix that I missed and we are good to go.

@ruebot
Copy link
Member

ruebot left a comment

This variable is the most important, and the only variable you need to change to see a complete set of visualizations for your Archives Unleashed Cloud Derivatives.

Lower case derivatives, and might as well link to this https://cloud.archivesunleashed.org/derivatives

  • Inconsistent use of full stops and capitalization on comments. Please put full stops on all comments, and captialize the first word. We don't want to undo #22.

  • Fix the comment with OUTPUT_FILENAME again. Inconsistent variables in comment and code.

  • Be consistent with whitespace below a comment. Sometimes there is a blank line, sometimes there isn't one. Choose one or the other.

  • Cell 32 needs a leading comment.

  • Cell 32 needs a leading comment, and white space at the beginning of the line.

  • Cell 34 needs a leading comment.

  • Cell 36 needs a leading comment.

  • Cell 39 needs a leading comment.

  • Cell 43 needs a leading comment.

  • Cell 45 needs a leading comment.

  • Cell 47 needs a leading comment.

  • Cell 51 needs a leading comment.

  • Cell 52 needs a leading comment.

  • Cell 53 needs a leading comment.

  • NetworkX citation is missing a full stop at the end.

@ianmilligan1
Copy link
Member

ianmilligan1 left a comment

Looking good on my end.

I missed this earlier, but I think we should also pop out the user-defined variable for cell 38. SELECT_DOMAIN or something like that? Maybe markdown above cell 38 explaining the variable, then a single-line cell with a variable to set?

@greebie

This comment has been minimized.

Copy link
Collaborator Author

greebie commented Mar 7, 2019

I did a weird thing with OUTPUT_FILENAME. I set it so that filename is TEXT_OUTPUT_FILENAME if that is set, otherwise it uses OUTPUT_FILENAME. Next commit will fix periods etc.

@ruebot

This comment has been minimized.

Copy link
Member

ruebot commented Mar 7, 2019

@greebie can you update the branch too?

greebie added some commits Mar 7, 2019

@ruebot
Copy link
Member

ruebot left a comment

Still have inconsistent capitalization and missing full stops on a number of comments.

@ruebot
Copy link
Member

ruebot left a comment

  • Cell 3: Still missing full stops on a few of the comments.
  • Cell 4: Capitalize the first work on the first five in-line comments.
  • Cell 23: Still missing full stops on in-line comments, and the first word needs to be capitalized in a few.
  • Cell 24: Capitalize the first work on the last three in-line comments.
  • Cell 25: First in-line comment missing a full-stop.
  • Cell 27: First in-line comment missing a full-stop.
  • NetworkX citation is still missing a full stop at the end.
@ruebot

ruebot approved these changes Mar 7, 2019

greebie added some commits Mar 7, 2019

@ianmilligan1 ianmilligan1 merged commit 3a873cc into master Mar 7, 2019

1 check passed

ci/dockercloud Your tests passed in Docker Cloud
Details

@ianmilligan1 ianmilligan1 deleted the issue-28 branch Mar 7, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.