March 2021 - petsc-dev - mailman3.cels.anl.gov

Fwd: [MCS-PI] Cerebras AI Training workshop
by Barry Smith 08 Mar '21

08 Mar '21

PETSc folks, This actually seems like a pretty interesting machine for PETSc. It seems ANL has had it for a very long time but kept it off the website and didn't provide much access except to chosen people. It would be great if at least one PETSc person could attend to see if there are possibilities, though the course may focus exclusively on ML type workloads. Barry > Begin forwarded message: > > From: "Taylor, Valerie E." <vtaylor(a)anl.gov> > Subject: [MCS-PI] FW: Cerebras AI Training workshop > Date: March 8, 2021 at 8:31:27 PM CST > To: "mcs-pi(a)mcs.anl.gov" <mcs-pi(a)mcs.anl.gov>, "postdocs(a)mcs.anl.gov" <postdocs(a)mcs.anl.gov> > Message-Id: <DF10FF2B-21D6-4C03-B0B2-08219115AAE0(a)anl.gov> > > Hello Everyone: > > Below, please find details about a two-day Argonne user training workshop for Cerebras. Registration is required. There will be more training sessions in the near future. > > --Valerie > > From: Venkatram Vishwanath <venkat(a)anl.gov <mailto:[email protected]>> > Date: Monday, March 8, 2021 at 1:14 PM > To: "Taylor, Valerie E." <vtaylor(a)anl.gov <mailto:[email protected]>>, Ian Foster <foster(a)anl.gov <mailto:[email protected]>>, "Habib, Salman" <habib(a)anl.gov <mailto:[email protected]>>, "Papka, Michael E." <papka(a)anl.gov <mailto:[email protected]>>, Rick Stevens <stevens(a)anl.gov <mailto:[email protected]>> > Cc: Venkatram Vishwanath <venkat(a)anl.gov <mailto:[email protected]>>, "Thakur, Rajeev" <thakur(a)anl.gov <mailto:[email protected]>>, "Emani, Murali Krishna" <memani(a)anl.gov <mailto:[email protected]>> > Subject: Cerebras AI Training workshop > > Dear All, > > We will be hosting a two-day Argonne user training workshop for the Cerebras AI system on March 22 (Mon) and March 23 (Tuesday). This will be held from 12:00 PM to ~4:00 PM each day and will be virtual. > > Here is a link to the registration page and we will share the meeting link with the accepted registrants. > https://events.cels.anl.gov/event/97/ <https://events.cels.anl.gov/event/97/> > > For the training, we will provide an overview of the Cerebras hardware and the software stack. We will demonstrate how one can log into the system, run sample examples, and get started on the system. Detailed agenda is on the registration page. We expect attendees to be very hands-on, port their science deep-learning workloads to run on the system, provide feedback on the system and contribute to the training materials. We expect to have more training sessions in the near future as well. > > We plan to target this training session for users willing to be very much hands-on. We may need to filter attendees based on the number of registrants for improved workshop experience and given system constraints. > > Please do forward this to others who will benefit from attending this. Do let us know if you have any questions and feel free to reach out to us. > > Best regards, > Murali, Rajeev and Venkat > _______________________________________________ > MCS-PI mailing list > MCS-PI(a)lists.mcs.anl.gov <mailto:[email protected]> > https://lists.mcs.anl.gov/mailman/listinfo/mcs-pi <https://lists.mcs.anl.gov/mailman/listinfo/mcs-pi>

1 0

Re: [petsc-dev] plan to transition to new documentation and webpages?
by Barry Smith 08 Mar '21

08 Mar '21

I think it is time to stop completely distributing docs with tarballs. Most people don't know they are there and how to access them so use google anyways. Also we should build release docs on release and main docs on main and forget the headaches of trying to put some new stuff in with the old. Then the only thing the tarball includes besides what is in git is the Fortran, petsc4py? interfaces. Has there been any issues with sowing bfort support portability in many years? petsc4py must need cpython, but does it need it for the tarball or is all of that pre-built when the tarball is made? I would advocate trying a release where the tarball is the git repository and see what happens. The current API says users would need to use --download-sowing but we could automatically turn that on if Fortran interfaces are requested. If we have tons of error reports with sowing we could revert and put the Fortran stubs back in. (Windows might be a problematic system). Time to clean house and simplify, Barry > On Mar 7, 2021, at 2:01 PM, Satish Balay <balay(a)mcs.anl.gov> wrote: > > Some notes on previous organization: > > - We have separate docs (manual, manpages, etc) for each petsc release > https://www.mcs.anl.gov/petsc/petsc-3.14/docs/ > https://www.mcs.anl.gov/petsc/petsc-main/docs/ > - the website (including developer docs, faq etc) primarily was built from 'main' branch. > Only the following website docs were synced from 'release' branch: > * documentation/index.html > * documentation/installation.html > * exclude=download/index.html > - All the website docs are also part of the release tarball (formatted differently), > so these versions are also available [perhaps this part needs preserving] > https://www.mcs.anl.gov/petsc/documentation/installation.html > vs > https://www.mcs.anl.gov/petsc/petsc-3.12/docs/installation.html > > Satish > > > On Sun, 7 Mar 2021, Patrick Sanan wrote: > >> Here's my WIP on having the sphinx build include a consistent set of HTML pages from the "classic" docs build. >> https://gitlab.com/petsc/petsc/-/merge_requests/3684 <https://gitlab.com/petsc/petsc/-/merge_requests/3684> >> >> >> >>> Am 07.03.2021 um 08:37 schrieb Patrick Sanan <patrick.sanan(a)gmail.com>: >>> >>> I'm working on this right now - I think I have a workable way, where we just use the "classic" docs system to build the man pages and HTML sources for each version on RTD, and then specify those HTML files as "extra" to Sphinx, so it just copies them over in the build and we can refer to them with local links (and their internal relative links work). Hopefully I can have a demo in the next couple of days. >>> >>>> Am 06.03.2021 um 19:33 schrieb Satish Balay via petsc-dev <petsc-dev(a)mcs.anl.gov>: >>>> >>>> This is partly due to the complexity of having some docs from 'release' and some from 'main' branches. >>>> >>>> We had a way to manage this when all docs were on petsc website - but its not clear how to do this properly with readthedocs >>>> >>>> Satish >>>> >>>> On Fri, 5 Mar 2021, Barry Smith wrote: >>>> >>>>> >>>>> What is the plan to transition to the new documentation and webpages? >>>>> >>>>> I go to https://www.mcs.anl.gov/petsc/index.html <https://www.mcs.anl.gov/petsc/index.html> and mostly see the old stuff etc. Our next release is coming up soon and it would be nice to have transitioned out of the old material and to the new material by/at the new release. >>>>> >>>>> What do we need to do to make this happen? >>>>> >>>>> Thanks >>>>> >>>>> Barry >>>>> >>>>> >>>> >>> >> >> >

1 0

Re: [petsc-dev] plan to transition to new documentation and webpages?
by Patrick Sanan 07 Mar '21

07 Mar '21

> Am 07.03.2021 um 01:01 schrieb Barry Smith <bsmith(a)petsc.dev>: > > > >> On Mar 6, 2021, at 4:46 PM, Jed Brown <jed(a)jedbrown.org <mailto:[email protected]>> wrote: >> >> The one value-add that comes from ReadTheDocs is its version switcher, which we'd need to do ourselves. > >> >> I've been using this strategy (for stand-alone preview) on a different project and it's working great. We can decide how to merge it (i.e., where the doc job should run). >> >> https://gitlab.com/petsc/petsc/-/merge_requests/3523 <https://gitlab.com/petsc/petsc/-/merge_requests/3523> > > This seems fine if it builds all the docs, manual pages, HTML of source code etc. But it doesn't seem to have anything to do with ReadTheDocs? It is not worth arguing over whether this special build takes place on a cloud machine or an MCS machine IMHO; the only question is where the resulting hundreds of megabytes of webpages end up. Can we just have them as artifacts on gitlab.com/petsc/petsc <http://gitlab.com/petsc/petsc> ? I am fine with that if it works. >> >> I think we should run https://petsc.org <https://petsc.org/> from docs generated on main using Sphinx. > > I think Satish's question is what about after a release? Does https://petsc.org <https://petsc.org/> point to docs built from release or main? Some users will want release but others will want main. Currently I think we have tricks that use a combination of information from both in a couple of places. > > What about all the other parts of docs not built using Spinx, manual pages, html source? > >> We can link to the old site for older versions. I'd be in favor of making https://mcs.anl.gov/petsc <https://mcs.anl.gov/petsc> (but not its subdirectories) redirect to petsc.org <http://petsc.org/>. > > That seems ok to me; but will we need to retrain Google, currently it knows which is the "best" webpage for everything in PETSc (like KSPSolve etc) as being at www.mcs.anl.gov/petsc <http://www.mcs.anl.gov/petsc>/... so we need to update the docs to start from https://petsc.org/ <https://petsc.org/> > > > We need to start making decisions. They seem to be > > 1) On what physical system are all the docs, Spinx, manual pages, html source actually existing on? > > Choices? gitlab.com <http://gitlab.com/> (as artifacts or something else), ReadTheDocs (can it handle storing the the non-Spinx?), ANL (drawback, only someone with an account can get them onto the system), something else? As far as I can tell so far, RTD can handle the extra HTML pages (my current WIP builds them all, but doesn't move them over to the final location - that might be slow and I don't know if there's a size limit I didn't read about yet). One thing RTD gives us (I think) is a nicer search feature. That's been quite useful for me searching the docs, e.g. https://docs.petsc.org/en/latest/search/?q=pc_type <https://docs.petsc.org/en/latest/search/?q=pc_type> There are definite downsides to not having as much control, though. > > 2) How are all the docs (Spinx and not) built to go into the physical system they will be on? > > Choices? gitlab.com <http://gitlab.com/> (nice, since anyone can trigger their building), ReadTheDocs (again nice that anyone can trigger their building, but can they do the non-Spinx easily?), ANL machine (bad, since requires someone with an account to trigger their build and/or storage). something else? My personal jury is still out on how easy it can be to do the complete build on RTD (see WIP MR https://docs.petsc.org/en/latest/search/?q=pc_type <https://docs.petsc.org/en/latest/search/?q=pc_type>). > > 3) Does the default point completely to docs built on release? Or built on main? Or built on some strange combination? > > Regardless of these questions I think we agree https://petsc.org/ <https://petsc.org/> (and https://mcs.anl.gov/petsc <https://mcs.anl.gov/petsc> by linking) will be how people find the docs. > Yes, though maybe It's tempting to build at mcs.anl.gov/petsc <http://mcs.anl.gov/petsc> so that pages with the same content could even have the same URLs, which would be nice for any external links that exist, and search engines' data on the man pages. > >> >> Barry Smith <bsmith(a)petsc.dev <mailto:[email protected]>> writes: >> >>> Is the plan still to use ReadTheDocs (which does support multiple versions of all the docs) or to "build them ourselves"? All ReadTheDocs does is run a Sphinx document builder script the user provides and we can do that ourselves and don't need ReadTheDocs to do it for us. In fact, if we do it ourselves we have much more flexibility since you ware not restricted to running only a Sphinx document builder script. >>> >>> Patrick, Jacob and others have done a fantastic job moving a lot of material into much better pages, it seems nuts not to be using it all. >>> >>> Barry >>> >>> >>>> On Mar 6, 2021, at 12:33 PM, Satish Balay <balay(a)mcs.anl.gov <mailto:[email protected]>> wrote: >>>> >>>> This is partly due to the complexity of having some docs from 'release' and some from 'main' branches. >>>> >>>> We had a way to manage this when all docs were on petsc website - but its not clear how to do this properly with readthedocs >>>> >>>> Satish >>>> >>>> On Fri, 5 Mar 2021, Barry Smith wrote: >>>> >>>>> >>>>> What is the plan to transition to the new documentation and webpages? >>>>> >>>>> I go to https://www.mcs.anl.gov/petsc/index.html <https://www.mcs.anl.gov/petsc/index.html> <https://www.mcs.anl.gov/petsc/index.html <https://www.mcs.anl.gov/petsc/index.html>> and mostly see the old stuff etc. Our next release is coming up soon and it would be nice to have transitioned out of the old material and to the new material by/at the new release. >>>>> >>>>> What do we need to do to make this happen? >>>>> >>>>> Thanks >>>>> >>>>> Barry >>>>> >>>>> >>>> >

1 0

Re: [petsc-dev] plan to transition to new documentation and webpages?
by Satish Balay 07 Mar '21

07 Mar '21

Some notes on previous organization: - We have separate docs (manual, manpages, etc) for each petsc release https://www.mcs.anl.gov/petsc/petsc-3.14/docs/ https://www.mcs.anl.gov/petsc/petsc-main/docs/ - the website (including developer docs, faq etc) primarily was built from 'main' branch. Only the following website docs were synced from 'release' branch: * documentation/index.html * documentation/installation.html * exclude=download/index.html - All the website docs are also part of the release tarball (formatted differently), so these versions are also available [perhaps this part needs preserving] https://www.mcs.anl.gov/petsc/documentation/installation.html vs https://www.mcs.anl.gov/petsc/petsc-3.12/docs/installation.html Satish On Sun, 7 Mar 2021, Patrick Sanan wrote: > Here's my WIP on having the sphinx build include a consistent set of HTML pages from the "classic" docs build. > https://gitlab.com/petsc/petsc/-/merge_requests/3684 <https://gitlab.com/petsc/petsc/-/merge_requests/3684> > > > > > Am 07.03.2021 um 08:37 schrieb Patrick Sanan <patrick.sanan(a)gmail.com>: > > > > I'm working on this right now - I think I have a workable way, where we just use the "classic" docs system to build the man pages and HTML sources for each version on RTD, and then specify those HTML files as "extra" to Sphinx, so it just copies them over in the build and we can refer to them with local links (and their internal relative links work). Hopefully I can have a demo in the next couple of days. > > > >> Am 06.03.2021 um 19:33 schrieb Satish Balay via petsc-dev <petsc-dev(a)mcs.anl.gov>: > >> > >> This is partly due to the complexity of having some docs from 'release' and some from 'main' branches. > >> > >> We had a way to manage this when all docs were on petsc website - but its not clear how to do this properly with readthedocs > >> > >> Satish > >> > >> On Fri, 5 Mar 2021, Barry Smith wrote: > >> > >>> > >>> What is the plan to transition to the new documentation and webpages? > >>> > >>> I go to https://www.mcs.anl.gov/petsc/index.html <https://www.mcs.anl.gov/petsc/index.html> and mostly see the old stuff etc. Our next release is coming up soon and it would be nice to have transitioned out of the old material and to the new material by/at the new release. > >>> > >>> What do we need to do to make this happen? > >>> > >>> Thanks > >>> > >>> Barry > >>> > >>> > >> > > > >

1 0

Re: [petsc-dev] plan to transition to new documentation and webpages?
by Patrick Sanan 07 Mar '21

07 Mar '21

Here's my WIP on having the sphinx build include a consistent set of HTML pages from the "classic" docs build. https://gitlab.com/petsc/petsc/-/merge_requests/3684 <https://gitlab.com/petsc/petsc/-/merge_requests/3684> > Am 07.03.2021 um 08:37 schrieb Patrick Sanan <patrick.sanan(a)gmail.com>: > > I'm working on this right now - I think I have a workable way, where we just use the "classic" docs system to build the man pages and HTML sources for each version on RTD, and then specify those HTML files as "extra" to Sphinx, so it just copies them over in the build and we can refer to them with local links (and their internal relative links work). Hopefully I can have a demo in the next couple of days. > >> Am 06.03.2021 um 19:33 schrieb Satish Balay via petsc-dev <petsc-dev(a)mcs.anl.gov>: >> >> This is partly due to the complexity of having some docs from 'release' and some from 'main' branches. >> >> We had a way to manage this when all docs were on petsc website - but its not clear how to do this properly with readthedocs >> >> Satish >> >> On Fri, 5 Mar 2021, Barry Smith wrote: >> >>> >>> What is the plan to transition to the new documentation and webpages? >>> >>> I go to https://www.mcs.anl.gov/petsc/index.html <https://www.mcs.anl.gov/petsc/index.html> and mostly see the old stuff etc. Our next release is coming up soon and it would be nice to have transitioned out of the old material and to the new material by/at the new release. >>> >>> What do we need to do to make this happen? >>> >>> Thanks >>> >>> Barry >>> >>> >> >

1 0

Re: [petsc-dev] plan to transition to new documentation and webpages?
by Barry Smith 07 Mar '21

07 Mar '21

Awesome, thanks for look at this. Barry > On Mar 7, 2021, at 1:37 AM, Patrick Sanan <patrick.sanan(a)gmail.com> wrote: > > I'm working on this right now - I think I have a workable way, where we just use the "classic" docs system to build the man pages and HTML sources for each version on RTD, and then specify those HTML files as "extra" to Sphinx, so it just copies them over in the build and we can refer to them with local links (and their internal relative links work). Hopefully I can have a demo in the next couple of days. > >> Am 06.03.2021 um 19:33 schrieb Satish Balay via petsc-dev <petsc-dev(a)mcs.anl.gov>: >> >> This is partly due to the complexity of having some docs from 'release' and some from 'main' branches. >> >> We had a way to manage this when all docs were on petsc website - but its not clear how to do this properly with readthedocs >> >> Satish >> >> On Fri, 5 Mar 2021, Barry Smith wrote: >> >>> >>> What is the plan to transition to the new documentation and webpages? >>> >>> I go to https://www.mcs.anl.gov/petsc/index.html <https://www.mcs.anl.gov/petsc/index.html> and mostly see the old stuff etc. Our next release is coming up soon and it would be nice to have transitioned out of the old material and to the new material by/at the new release. >>> >>> What do we need to do to make this happen? >>> >>> Thanks >>> >>> Barry >>> >>> >> >

1 0

Re: [petsc-dev] plan to transition to new documentation and webpages?
by Patrick Sanan 07 Mar '21

07 Mar '21

I'm working on this right now - I think I have a workable way, where we just use the "classic" docs system to build the man pages and HTML sources for each version on RTD, and then specify those HTML files as "extra" to Sphinx, so it just copies them over in the build and we can refer to them with local links (and their internal relative links work). Hopefully I can have a demo in the next couple of days. > Am 06.03.2021 um 19:33 schrieb Satish Balay via petsc-dev <petsc-dev(a)mcs.anl.gov>: > > This is partly due to the complexity of having some docs from 'release' and some from 'main' branches. > > We had a way to manage this when all docs were on petsc website - but its not clear how to do this properly with readthedocs > > Satish > > On Fri, 5 Mar 2021, Barry Smith wrote: > >> >> What is the plan to transition to the new documentation and webpages? >> >> I go to https://www.mcs.anl.gov/petsc/index.html <https://www.mcs.anl.gov/petsc/index.html> and mostly see the old stuff etc. Our next release is coming up soon and it would be nice to have transitioned out of the old material and to the new material by/at the new release. >> >> What do we need to do to make this happen? >> >> Thanks >> >> Barry >> >> >

1 0

Re: [petsc-dev] plan to transition to new documentation and webpages?
by Barry Smith 06 Mar '21

06 Mar '21

> On Mar 6, 2021, at 4:46 PM, Jed Brown <jed(a)jedbrown.org> wrote: > > The one value-add that comes from ReadTheDocs is its version switcher, which we'd need to do ourselves. > > I've been using this strategy (for stand-alone preview) on a different project and it's working great. We can decide how to merge it (i.e., where the doc job should run). > > https://gitlab.com/petsc/petsc/-/merge_requests/3523 This seems fine if it builds all the docs, manual pages, HTML of source code etc. But it doesn't seem to have anything to do with ReadTheDocs? It is not worth arguing over whether this special build takes place on a cloud machine or an MCS machine IMHO; the only question is where the resulting hundreds of megabytes of webpages end up. Can we just have them as artifacts on gitlab.com/petsc/petsc <http://gitlab.com/petsc/petsc> ? I am fine with that if it works. > > I think we should run https://petsc.org from docs generated on main using Sphinx. I think Satish's question is what about after a release? Does https://petsc.org <https://petsc.org/> point to docs built from release or main? Some users will want release but others will want main. Currently I think we have tricks that use a combination of information from both in a couple of places. What about all the other parts of docs not built using Spinx, manual pages, html source? > We can link to the old site for older versions. I'd be in favor of making https://mcs.anl.gov/petsc (but not its subdirectories) redirect to petsc.org. That seems ok to me; but will we need to retrain Google, currently it knows which is the "best" webpage for everything in PETSc (like KSPSolve etc) as being at www.mcs.anl.gov/petsc <http://www.mcs.anl.gov/petsc>/... so we need to update the docs to start from https://petsc.org/ <https://petsc.org/> We need to start making decisions. They seem to be 1) On what physical system are all the docs, Spinx, manual pages, html source actually existing on? Choices? gitlab.com <http://gitlab.com/> (as artifacts or something else), ReadTheDocs (can it handle storing the the non-Spinx?), ANL (drawback, only someone with an account can get them onto the system), something else? 2) How are all the docs (Spinx and not) built to go into the physical system they will be on? Choices? gitlab.com <http://gitlab.com/> (nice, since anyone can trigger their building), ReadTheDocs (again nice that anyone can trigger their building, but can they do the non-Spinx easily?), ANL machine (bad, since requires someone with an account to trigger their build and/or storage). something else? 3) Does the default point completely to docs built on release? Or built on main? Or built on some strange combination? Regardless of these questions I think we agree https://petsc.org/ <https://petsc.org/> (and https://mcs.anl.gov/petsc <https://mcs.anl.gov/petsc> by linking) will be how people find the docs. > > Barry Smith <bsmith(a)petsc.dev> writes: > >> Is the plan still to use ReadTheDocs (which does support multiple versions of all the docs) or to "build them ourselves"? All ReadTheDocs does is run a Sphinx document builder script the user provides and we can do that ourselves and don't need ReadTheDocs to do it for us. In fact, if we do it ourselves we have much more flexibility since you ware not restricted to running only a Sphinx document builder script. >> >> Patrick, Jacob and others have done a fantastic job moving a lot of material into much better pages, it seems nuts not to be using it all. >> >> Barry >> >> >>> On Mar 6, 2021, at 12:33 PM, Satish Balay <balay(a)mcs.anl.gov> wrote: >>> >>> This is partly due to the complexity of having some docs from 'release' and some from 'main' branches. >>> >>> We had a way to manage this when all docs were on petsc website - but its not clear how to do this properly with readthedocs >>> >>> Satish >>> >>> On Fri, 5 Mar 2021, Barry Smith wrote: >>> >>>> >>>> What is the plan to transition to the new documentation and webpages? >>>> >>>> I go to https://www.mcs.anl.gov/petsc/index.html <https://www.mcs.anl.gov/petsc/index.html> and mostly see the old stuff etc. Our next release is coming up soon and it would be nice to have transitioned out of the old material and to the new material by/at the new release. >>>> >>>> What do we need to do to make this happen? >>>> >>>> Thanks >>>> >>>> Barry >>>> >>>> >>>

1 0

Re: [petsc-dev] plan to transition to new documentation and webpages?
by Jed Brown 06 Mar '21

06 Mar '21

The one value-add that comes from ReadTheDocs is its version switcher, which we'd need to do ourselves. I've been using this strategy (for stand-alone preview) on a different project and it's working great. We can decide how to merge it (i.e., where the doc job should run). https://gitlab.com/petsc/petsc/-/merge_requests/3523 I think we should run https://petsc.org from docs generated on main using Sphinx. We can link to the old site for older versions. I'd be in favor of making https://mcs.anl.gov/petsc (but not its subdirectories) redirect to petsc.org. Barry Smith <bsmith(a)petsc.dev> writes: > Is the plan still to use ReadTheDocs (which does support multiple versions of all the docs) or to "build them ourselves"? All ReadTheDocs does is run a Sphinx document builder script the user provides and we can do that ourselves and don't need ReadTheDocs to do it for us. In fact, if we do it ourselves we have much more flexibility since you ware not restricted to running only a Sphinx document builder script. > > Patrick, Jacob and others have done a fantastic job moving a lot of material into much better pages, it seems nuts not to be using it all. > > Barry > > >> On Mar 6, 2021, at 12:33 PM, Satish Balay <balay(a)mcs.anl.gov> wrote: >> >> This is partly due to the complexity of having some docs from 'release' and some from 'main' branches. >> >> We had a way to manage this when all docs were on petsc website - but its not clear how to do this properly with readthedocs >> >> Satish >> >> On Fri, 5 Mar 2021, Barry Smith wrote: >> >>> >>> What is the plan to transition to the new documentation and webpages? >>> >>> I go to https://www.mcs.anl.gov/petsc/index.html <https://www.mcs.anl.gov/petsc/index.html> and mostly see the old stuff etc. Our next release is coming up soon and it would be nice to have transitioned out of the old material and to the new material by/at the new release. >>> >>> What do we need to do to make this happen? >>> >>> Thanks >>> >>> Barry >>> >>> >>

1 0

Re: [petsc-dev] plan to transition to new documentation and webpages?
by Barry Smith 06 Mar '21

06 Mar '21

Is the plan still to use ReadTheDocs (which does support multiple versions of all the docs) or to "build them ourselves"? All ReadTheDocs does is run a Sphinx document builder script the user provides and we can do that ourselves and don't need ReadTheDocs to do it for us. In fact, if we do it ourselves we have much more flexibility since you ware not restricted to running only a Sphinx document builder script. Patrick, Jacob and others have done a fantastic job moving a lot of material into much better pages, it seems nuts not to be using it all. Barry > On Mar 6, 2021, at 12:33 PM, Satish Balay <balay(a)mcs.anl.gov> wrote: > > This is partly due to the complexity of having some docs from 'release' and some from 'main' branches. > > We had a way to manage this when all docs were on petsc website - but its not clear how to do this properly with readthedocs > > Satish > > On Fri, 5 Mar 2021, Barry Smith wrote: > >> >> What is the plan to transition to the new documentation and webpages? >> >> I go to https://www.mcs.anl.gov/petsc/index.html <https://www.mcs.anl.gov/petsc/index.html> and mostly see the old stuff etc. Our next release is coming up soon and it would be nice to have transitioned out of the old material and to the new material by/at the new release. >> >> What do we need to do to make this happen? >> >> Thanks >> >> Barry >> >> >

1 0