-
Notifications
You must be signed in to change notification settings - Fork 10
DOC: enhance documentation for first-time users #191
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Made a suggestion on the FAQ text to make it a little meatier.
Otherwise, LGTM! Let me know if there's any other places you want to touch up or if I should go ahead with a merge.
Codecov Report
@@ Coverage Diff @@
## v0.6.0 #191 +/- ##
=====================================
Coverage 78% 78%
=====================================
Files 19 19
Lines 1967 1967
Branches 315 315
=====================================
Hits 1548 1548
Misses 356 356
Partials 63 63 |
Let's hold off a little bit on merging; I'd like to at least get a basic test up and running. This PR can hold the documentation fixes I make in the meantime. I have perhaps a naive usage question. I have this script on def job(x):
return x
if __name__ == "__main__":
mapped = map(job, range(4))
results = list(mapped)
print(results)
import htmap as ht
future = ht.map(job, range(4))
print(future)
results = list(future)
print(results) I submit this script with a miniconda install on
Why isn't this working? |
Co-Authored-By: Josh Karpel <josh.karpel@gmail.com>
I snooped around in your It turns out you're falling through a crack in the mechanism that detects execution errors. The problem is that your Docker image doesn't have Basically, the problem is that HTMap is failing execute-side before it can manage to produce an execution error for you. I'm not quite sure how to tackle this, but I've created an issue to track it #194. For now, you probably need to make a new image (based on the one you're using) with |
Thank you – that resolved my issue. I've added some debugging tips in
I'll likely have more documentation changes in this process. I've modified PR title to reflect that. |
I've consolidates the tutorials and recipes into one page with a divider. I can't test this change right now (htcondor doesn't install on macOS). I did this because I remembered seeing a Docker tutorial, and spent a couple minutes looking for it. I first looked in "Tutorials", then I looked in "Dependency Management", then I bounced around a couple places before looking in the recipes. I moved it to the first place I looked. |
Seems quite reasonable! If you need an environment to build the docs in, the testing Docker container should just need the docs requirements installed in it to be able to do a docs build. Start the container by running I should probably encapsulate that in another container for ease of use... (I run into the same problem on Windows, since we don't have pip-installable HTCondor Python bindings on Windows). |
Quick thought - be careful on HTCondor documentation, because a lot of things ends up being site-specific. The That does make me think that we should eventually have a "HTMap in CHTC" page on https://github.com/CHTC/chtc-website-source where we can put that kind of information. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I love it! Comments have a bunch of small nitpicks/personal-preference edits, but I love the reorganization, and the wealth of little tips and tricks coming from your experience getting started is awesome.
Co-authored-by: Josh Karpel <josh.karpel@gmail.com>
Co-authored-by: Josh Karpel <josh.karpel@gmail.com>
Co-authored-by: Josh Karpel <josh.karpel@gmail.com>
Co-authored-by: Josh Karpel <josh.karpel@gmail.com>
Co-authored-by: Josh Karpel <josh.karpel@gmail.com>
Co-authored-by: Josh Karpel <josh.karpel@gmail.com>
Co-authored-by: Josh Karpel <josh.karpel@gmail.com>
Co-authored-by: Josh Karpel <josh.karpel@gmail.com>
Co-authored-by: Josh Karpel <josh.karpel@gmail.com>
Co-authored-by: Josh Karpel <josh.karpel@gmail.com>
Co-authored-by: Josh Karpel <josh.karpel@gmail.com>
Co-authored-by: Josh Karpel <josh.karpel@gmail.com>
Co-authored-by: Josh Karpel <josh.karpel@gmail.com>
Looks like everything is resolved! I'll let it simmer overnight for any final changes and merge it tomorrow. (Don't worry about the CI builds... there's a flaky test that I've been trying to hammer out.) |
I'll try to give it another review tonight too. |
Thank you so much @stsievert ! |
What does this PR implement?
It adds a link back to the HTCondor homepage on the front page of the HTMap documentation.
I was looking for a piece of documentation specific to HTCondor ("what does a HOLD tag on a job mean?"). I went looking for link back to the HTCondor documentation, and the front page was the first place I looked.
It also implements the following:
Map.component_by_status
All of these come from my first (real) usage of HTMap and HTCondor.
edit This PR will...
close Doc build throws an error on pandoc in docker machine #201