-
Notifications
You must be signed in to change notification settings - Fork 13
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
docs: FuncADL Query Type documentation links to reference not using current API #493
Comments
@RogerJanusiak is in the process of updating this. Also, the location of those things have moved, it isn't in my account any longer. I'll let Roger update you here. |
The first update to the documentation has been submitted. Many of the examples now use the new API versions. Also added warnings to pages with examples not updated. |
Note to self, the repo now is at https://github.com/iris-hep/xaod_usage with the book being published at https://iris-hep.org/xaod_usage/.
Done in PR iris-hep/xaod_usage#26 |
Since this has been addressed, closing this! Reopen if we missed something! |
@gordonwatts Is this fully addressed?
makes it sound like PR iris-hep/xaod_usage#26 is only a start. There are no other linking PRs here. @RogerJanusiak has everything been migrated now? |
The other PRs will take a long time, and some may not be done because the data in R21 no longer exists. But the simple stuff has already moved to 3.0. So, I suggest we keep this closed. There are now enough examples. |
As noted in iris-hep/analysis-systems-deliverables#1 (comment), the existing ServiceX client docs for FuncADL Query Type give @gordonwatts's https://github.com/gordonwatts/xaod_usage Jupyter Book as the full user docs reference.
ServiceX_frontend/docs/query_types.rst
Line 142 in 53226cd
However, that Jupyter Book isn't using the
v3.0.x
API, so this will be important to update. While these are docs outside of this repository, they should still be kept up to date. It isn't reasonable to ask @gordonwatts to be the sole maintainer of that, so it would be great if the other members of the ServiceX development team (who have the API flow through their fingers at the moment while some of us are still kickstarting it a bit) could help update this.The text was updated successfully, but these errors were encountered: