Thanks to visit codestin.com
Credit goes to github.com

Skip to content

DOC: Moved VQ example & target from duplicate array broadcasting doc #19369

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

Merged
merged 5 commits into from
Jul 18, 2021

Conversation

Mukulikaa
Copy link
Contributor

@Mukulikaa Mukulikaa commented Jun 28, 2021

Closes #19136

According to the plan discussed in the issue, I have added the vector quantization example to the main Broadcasting doc. I have tried to add some explanations to it from the EricsBroadcastingDoc (the original source of both the broadcasting docs).

In an attempt to accommodate references to the orphan doc, I have moved the sphinx cross-linking target to the main Broadcasting doc. I tested it locally and it works, but I'm not sure if it's best practice to do that.

I wanted some feedback on the crosslinking hack and whether the example reads like a tutorial. Thanks!
cc: @melissawm @rossbar

Copy link
Member

@melissawm melissawm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @Mukulikaa - I agree with doing this in pieces so I'm ok with it for now. I wonder though if it would just be easier to remove the part you already included in the main broadcasting document from the orphan page, so we don't redo the work later.


.. figure:: theory.broadcast_5.png
:alt: vector quantitization example
:name: figure-1
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the reason for the CI failure: this image name is referenced twice (here and in the other document). Can you change this "name" argument to something different?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! I was aware of that but decided to ignore it for now because eventually the other doc would be removed and it wouldn't clash anymore. But now that I think of it, I should use a different naming system e.g. "doc-name.figure no." so that it doesn't cause a problem later on when we include figures in other documents too.

Copy link
Contributor

@rossbar rossbar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder though if it would just be easier to remove the part you already included in the main broadcasting document from the orphan page, so we don't redo the work later.

+1 this would make it easier to keep track of what content has already been moved, especially if the full transfer will occur over multiple PRs.

@Mukulikaa Mukulikaa marked this pull request as ready for review June 30, 2021 21:17
@melissawm
Copy link
Member

Last (maybe nit?) suggestion: since we have moved content from this page to the basics.broadcasting document, might be useful to add a link to it from the array-broadcasting-in-numpy doc.

@Mukulikaa
Copy link
Contributor Author

I think it does make sense to do that for users who might land on the page through external sources. Does this mean we can never remove the array-broadcasting-in-numpy doc from the directory because it might break links in someone's blog or tutorial?

@melissawm
Copy link
Member

I think the test failure is unrelated.

1. Deleted older formats of the graphics which belonged to the orphan doc
2. Added SVGs for the same diagrams (with necessary corrections)
3. Added detailed alt-texts for each diagram and graph
4. Removed all content from the orphan doc since all of it has been moved
@Mukulikaa
Copy link
Contributor Author

Hi @MarsBarLee, I have converted all the diagrams in the doc to the SVG format and added alt-texts for them. It would be nice if you could review the doc once when you have time!

@MarsBarLee
Copy link
Contributor

Hi Mukulika, the alt-text and SVGs look good! Thank you for including those changes.

Copy link
Member

@melissawm melissawm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this looks really good, thanks @Mukulikaa !

Co-authored-by: Melissa Weber Mendonça <[email protected]>
@melissawm
Copy link
Member

@rossbar want to take a last look?

@mattip
Copy link
Member

mattip commented Jul 18, 2021

Here is the new page vs the old page

Here is the location of the old content, that page is now empty, but I guess it is good to keep it around for a few releases since other sites may be referencing it.

@mattip mattip merged commit 131b6bf into numpy:main Jul 18, 2021
@mattip
Copy link
Member

mattip commented Jul 18, 2021

Thanks @Mukulikaa

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DOC: Merging duplicate array broadcasting docs
5 participants