Split 10min.ipynb into cuDF-only and Dask-cuDF notebooks#21669
Split 10min.ipynb into cuDF-only and Dask-cuDF notebooks#21669Anas0709 wants to merge 4 commits intorapidsai:mainfrom
Conversation
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
|
Thank you for the pull request. Could you run the |
|
Hi @mroeschke, could you please add the |
| "id": "f5e303df", | ||
| "metadata": {}, | ||
| "outputs": [ |
There was a problem hiding this comment.
Could you ensure all these cells remain executed?
…sai#21374) - 10min.ipynb: cuDF-only content (no Dask) for CI validation - 10min_dask_cudf.ipynb: Dask-cuDF content for distributed GPU workflows - Added 10min_dask_cudf to user guide toctree Made-with: Cursor
…s to Dask notebook Made-with: Cursor
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Made-with: Cursor
Anas0709
force-pushed
the
fix/split-10min-notebook-21374
branch
from
72d92b5 to
bc282ef
Compare
|
Addressed the missing agg_col1/agg_col2 setup cell, it was omitted during the split and is now added before the Grouping section. I don’t have access to a RAPIDS GPU environment locally, so the cells still have empty outputs. I’m relying on RAPIDS CI to execute the notebook during the docs build. Let me know if you’d prefer a different approach. |
|
Sorry for the delay @Anas0709. Yes, we would prefer to avoid using the CI to incrementally validate notebook changes since it's a shared, limited resource. I would recommend using Google Colab to validate changes "locally" before we run them in CI. You can follow and modify the instructions in https://docs.rapids.ai/deployment/stable/platforms/colab/ on how to get set up with a GPU environment |
2 participants
Fixes
Splits the combined 10min notebook into:
The cuDF-only notebook can now be validated in CI, since it no longer uses Dask.
Changes: