Add the PyGMT talk at AGU24 to the "Overview" section

[yvonnefroehlich]

Description of proposed changes

List the PyGMT talk at AGU24 to the "Overview" section

• Create and add thumbnail image
  - Orientation on existing thumbnails, used a photo @weiji14 made
  - Better link to an image, to avoid including large files into the repo
• Upload slides to figshare to create a DOI
  - http://dx.doi.org/10.6084/m9.figshare.28049495
  - Recordings are not freely available, do not include an image of the presenter, and are not linked with the slides
• Upload abstract to ResearchGate
  - https://www.researchgate.net/publication/387127897_PyGMT_-_Accessing_and_Integrating_GMT_with_Python_and_the_Scientific_Python_Ecosystem

Preview: https://pygmt-dev--3685.org.readthedocs.build/en/3685/overview.html

Fixes: #3683 (partly)

Reminders

• Run make format and make check to make sure the code follows the style guide.
• Add tests for new features or tests that would have caught the bug that you're fixing.
• Add new public functions/methods/classes to doc/api/index.rst.
• Write detailed docstrings for all functions/methods.
• If wrapping a new module, open a 'Wrap new GMT module' issue and submit reasonably-sized PRs.
• If adding new functionality, add an example to docstrings or tutorials.
• Use underscores (not hyphens) in names of Python files and directories.

Slash Commands

You can write slash commands (/command) in the first line of a comment to perform
specific operations. Supported slash command is:

• /format: automatically format and lint the code

[yvonnefroehlich]

/format

[seisman]

Two notes:

1. @maxrjones once proposed to move all presentations to the "External Resources" and had some ideas about what to be included in the overview page (Remove Liam's talk from the overview page #1764 (comment)). I'm unsure if @maxrjones still remembers the ideas.

2. As previously mentioned in Add SciPy 2022 talk to presentations #2053 (comment), I feel we should not add large binary files/images into this repository. Even if we decide to add, we should compress the image using tools like https://squoosh.app/

[yvonnefroehlich]

2. As previously mentioned in Add SciPy 2022 talk to presentations #2053 (comment), I feel we should not add large binary files/images into this repository. Even if we decide to add, we should compress the image using tools like https://squoosh.app/

Hm. I also was a bit wondering about the sizes of the image files. But when comparing the image added newly in the PR with the already included images, the file size is in the same range:

I reduced the size of my image via the tool @seisman mentioned and now it is 140 KB large.

[yvonnefroehlich]

1. @maxrjones once proposed to move all presentations to the "External Resources" and had some ideas about what to be included in the overview page (Remove Liam's talk from the overview page #1764 (comment)). I'm unsure if @maxrjones still remembers the ideas.

Yes, adding the conference contributions to the “overview” section is not directly intuitive. But maybe the idea of adding these materials to the overview page was to show how the PyGMT project developed over time (instead of any kind of history section). Some of these contributions are more an overview of the main ideas and aims of the project rather than a more detailed presentation on PyGMT.

[seisman]

2. As previously mentioned in Add SciPy 2022 talk to presentations #2053 (comment), I feel we should not add large binary files/images into this repository. Even if we decide to add, we should compress the image using tools like https://squoosh.app/

Hm. I also was a bit wondering about the the sizes of the image files. But when comparing the image added newly in the PR with the already included images, the file size is in the same range:

I reduced the size of my image via the tool @seisman mentioned and now it is 140 KB large.

These large images were added at the very early stage of the project and I think that's not a good practice.

[yvonnefroehlich]

These large images were added at the very early stage of the project and I think that's not a good practice.

Then we probably have to discuss / decide if we want to keep / continue the list of conference contributions as is or remove these images from the repo. Or we find a solution where we can just link to an image which serves as thumbnail image.

[weiji14]

Or we find a solution where we can just link to an image which serves as thumbnail image.

If you are planning to upload your slides to Figshare or ResearchGate to create a DOI, you can also upload the thumbnail image there, and we can link to that instead of uploading the thumbnail to the PyGMT repo?

[yvonnefroehlich]

Or we find a solution where we can just link to an image which serves as thumbnail image.

If you are planning to upload your slides to Figshare or ResearchGate to create a DOI, you can also upload the thumbnail image there, and we can link to that instead of uploading the thumbnail to the PyGMT repo?

I added the title and summery slides as figures on RG (https://www.researchgate.net/publication/387127897_PyGMT_-_Accessing_and_Integrating_GMT_with_Python_and_the_Scientific_Python_Ecosystem/figures) and linked the title slide for the overview section in the PyGMT docs (commit 262d6d4).

[yvonnefroehlich]

In commit 8ffb788, I tried to link to the thumbnail images provided by figshare. In principle this works, however the resolution is quite poor. In commit 12dd4fb, I reduced the width of the images to see if this helps.

This would be a way to be able to remove the large images stored in the repo, except "doc/_static/scipy2022-youtube-thumbnail.jpg", as this one is also used in the README.

[seisman]

The easiest solution is to upload the static images into the comment box, and then GitHub will store them for us, just like what we're doing in https://github.com/GenericMappingTools/pygmt/blob/main/doc/external_resources.md,

[weiji14]

For the images files 2022 and older, they have already been commited to the git history, so removing them won't actually reduce the download size when doing a git clone. So you can revert the changes here and in the lines below.

[weiji14]

The easiest solution is to upload the static images into the comment box, and then GitHub will store them for us, just like what we're doing in https://github.com/GenericMappingTools/pygmt/blob/main/doc/external_resources.md,

I use this trick all the time too, but I'm never sure how stable this actually is. What I'd recommend is to upload the full resolution thumbnail image to figshare (see e.g. how I uploaded a PNG thumbnail and PDF version of my MIGARS poster) just in case. We can still use the GitHub link, but if that image ever disappears accidentally, we can retrieve it from figshare again.

[seisman]

What I'd recommend is to upload the full resolution thumbnail image to figshare (see e.g. how I uploaded a PNG thumbnail and PDF version of my MIGARS poster) just in case. We can still use the GitHub link, but if that image ever disappears accidentally, we can retrieve it from figshare again.

Or we can create a separate github repository to store these static images.

[yvonnefroehlich]

Maybe merge this PR and open a separat issue (and PR) for this?

[seisman]

yes, we can discuss it later

[yvonnefroehlich]

I opened issue to not forget about this #3708.

[yvonnefroehlich]

The easiest solution is to upload the static images into the comment box, and then GitHub will store them for us, just like what we're doing in https://github.com/GenericMappingTools/pygmt/blob/main/doc/external_resources.md,

Actually, I tried this directly at the beginning of this PR in commit c7c3228. But for me, the URL related to the image is not in the form https://user-images.githubusercontent.com/XYZ.png but in https://private-user-images.githubusercontent.com/XYZ.png?ABC. I remember that I faced this issue before, but could not figure out what I have to change on my side.

[seisman]

Here is the link that can be used: https://github.com/user-attachments/assets/19e1391e-648d-43da-b6f6-ecfb4f3e83e8