MHKiT-Software / MHKiT

MHKiT Documentation
https://MHKiT-Software.github.io/MHKiT/
4 stars 14 forks source link

Doc updates 1 #60

Closed akeeste closed 6 months ago

akeeste commented 6 months ago

This PR

akeeste commented 6 months ago

I've updated this PR to include the latest PRs into master. It seems like #54 should already be resolved upon building the docs, but I'm getting errors doing that.

Right now reading mhkit-matlab/api.river.rst gives an error for some reason. I'm using a new environment with Python 3.11

simmsa commented 6 months ago

@akeeste, sorry for not pointing this out earlier. The fix is here: https://github.com/MHKiT-Software/MHKiT/pull/58/commits/1896ee1963185f653e79325d651133ed9c224b2f. Annoyingly it seems like some sphinx function is case sensitive.

akeeste commented 6 months ago

@simmsa Thanks! I don't see that commit on the master branch but added it to this PR.

The mooring module is now showing up, but has some incorrect formatting within the example so it shows up on the table of contents incorrectly.

akeeste commented 6 months ago

@simmsa can you give this a review? I have not rebuilt the docs yet so that the changes are easier to review. If things look good, I'll rebuild, double check for issues, then move on to some reorganization tasks I want to address.

simmsa commented 6 months ago

@akeeste, this looks good to me, nice work! My only question is related to the second note within the python installation instructions. Is this note still necessary (screenshot below)? MacOS Removed Python 2.7 Support in Monterey 12.3 on 3/14/2023 so maybe now is a good time to remove this section? To me this feels outdated. Screenshot 2024-05-14 at 4 50 04 PM

akeeste commented 6 months ago

Thanks @simmsa. Agreed, I'll remove that not about Python 2.7 on Mac. I'm also going to remove the note about adding python to the path during installation. This is not required to install or use MHKiT. We should leave it up to the user to install Python correctly.

simmsa commented 6 months ago

@akeeste, I agree with removing the windows path section. I pulled this branch locally verified that everything looks correct. I don't see any formatting or build errors. Nice work!

akeeste commented 6 months ago

FYI I tried to do something clever here with submodules, which make the automated build/deployment fail. I reverted the python submodule to master so that the updated docs deploy. But the mooring example will not show up accurately.

simmsa commented 6 months ago

Good fix! For me the mooring example looks and performs nominally in the deployed docs on Chrome. The rendering method of the animations does seems fragile, but it looks like it works.

akeeste commented 6 months ago

Noting what I did in this PR and then here because the automated build/deploy is not performing as I would expect. Something weird is happening.

In this PR I:

Then:

So, there seems to be an issue with the automated building. The deployed docs are not those being automatically built, but those being manually built and committed. This would also explain why #54 had to be opened even though the mooring example was called out in python.rst in v0.7.0