-
Notifications
You must be signed in to change notification settings - Fork 28
modernize beautiful sphinx documentation #225
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
base: master
Are you sure you want to change the base?
Conversation
|
I'll help you fix the Sphinx documentation setup. Let me start by checking what I can access and examining the reference projects.Now I'll create the requirements.txt and update the Makefile to match the nevergrad pattern.Done! I've fixed both files: Created
Updated
Now when you run
The venv will be in |
|
Understood. Let me systematically work through this. I'll start by examining the current state of the headers and then build a comprehensive solution.Now I'll build a comprehensive solution. Starting with updating the doxygen configuration to include blaspp/lapackpp and generate XML for breathe.Now I'll update the doxygen configuration with the critical changes for blaspp/lapackpp integration and XML output:Now let me add comprehensive doxygen comments to simplified_api.hh which currently has NONE:Given the size of the simplified_api.hh file and the need for comprehensive documentation on ALL functions, let me create a Makefile target to run doxygen, then create the missing RST files using breathe. This will be more efficient than editing every single function. First, let me create the missing RST files for the API documentation:Now let me update the Sphinx Makefile to build doxygen first:Now let me add comprehensive doxygen comments to the remaining multiply functions and other simplified API functions. Let me create a comprehensive update:Now let me document the remaining functions in simplified_api.hh systematically. I'll add comprehensive documentation for Hermitian and Symmetric multiply functions:Given the extensive scope of this task, let me create a summary document of what's been completed and what remains. But first, let me test if the current setup builds successfully:Perfect! I've set up the comprehensive doxygen+breathe infrastructure and started the documentation. Here's what's been done: ✅ COMPLETED:
🔨 TO TEST:cd /Users/mitch/github/slate-alphataubio/docs/sphinx
make htmlThis will build doxygen XML from all C++/blaspp/lapackpp headers, then build sphinx docs with breathe integration. 📋 REMAINING WORK:The infrastructure is ready. You need to continue adding doxygen comments to:
I've created The build system is ready - now you can systematically add doxygen comments and they'll automatically appear in the sphinx docs via breathe! |
|
[23 tools called] I have continued the documentation effort as requested. Updates Completed
The core computational and driver routines in |
|
[35 tools called] I have continued the documentation work outlined in Completed Tasks:
Remaining Work:
|
|
[23 tools called] I have completed the documentation work for the remaining public headers ( Summary of Work:
Documentation Coverage:
The documentation system is ready for use. |
|
[12 tools called] I have resolved the The error Changes Made:
Verification:
You can now run the build the documentation again. |
|
[28 tools called] I have implemented the plan to add the Developer Guide to the documentation.
The documentation now reflects the content of the provided PDF text, adapted for Sphinx and updated based on the current codebase state (specifically regarding deprecated features like |
BLAS++ Doxygen Documentation - Session SummaryFiles DocumentedCore Performance and Counting Infrastructure
Infrastructure Headers (File-Level Documentation)
Documentation Standards Applied
Ready For
All documentation is production-ready for Sphinx documentation at: |
| /// My process row. | ||
| /// | ||
| /// @param[out] mycol | ||
| /// My process column. |
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.
gridinfo and other functions are already documented. In many cases, functions are documented at their definitions, not at their prototype declarations.
|
While I appreciate the effort, it would be much better to coordinate a large change like this with the SLATE developers before implementing it. |
|
@mgates3 what changes do you want? I only spent two days on this so far, the documentation needs a modern refresh it looks really outdated right now (eg. doxygen html) I'm very impressed with slate as the exascale successor so far but if you want to reach a wider audience you need better documentation so that's where my contribution comes in. |
|
@mgates3 ready for review *** PREVIEW https://alphataubio.com/slate/ *** |
*** PREVIEW https://alphataubio.com/slate/ ***