Skip to content

Conversation

@theabro
Copy link
Collaborator

@theabro theabro commented Nov 15, 2024

These are some initial suggestions for content for Episode 2 - Basics, primarily using the EPCC course as inspiration but simplifying things somewhat.

@github-actions
Copy link

github-actions bot commented Nov 15, 2024

Thank you!

Thank you for your pull request 😃

🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.

If you have files that automatically render output (e.g. R Markdown), then you should check for the following:

  • 🎯 correct output
  • 🖼️ correct figures
  • ❓ new warnings
  • ‼️ new errors

Rendered Changes

🔍 Inspect the changes: https://github.com/carpentries-incubator/intro-to-modern-fortran/compare/md-outputs..md-outputs-PR-29

The following changes were observed in the rendered markdown documents:

 02-variables.md (new)  | 482 +++++++++++++++++++++++++++++++++++++++
 03-maths.md (new)      | 608 +++++++++++++++++++++++++++++++++++++++++++++++++
 04-logic.md (new)      | 101 ++++++++
 05-strings.md (new)    |  26 +++
 config.yaml            |   6 +-
 data/exercises.tar.gz  | Bin 359 -> 5817 bytes
 discuss.md (new)       |  20 ++
 introduction.md (gone) | 220 ------------------
 md5sum.txt             |   8 +-
 9 files changed, 1247 insertions(+), 224 deletions(-)
What does this mean?

If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible.

This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation.

⏱️ Updated at 2025-05-19 09:20:21 +0000

github-actions bot pushed a commit that referenced this pull request Nov 15, 2024
@theabro theabro mentioned this pull request Nov 15, 2024
Comment on lines 128 to 138
program example3
implicit none

real, parameter :: pi = 3.14159265

end program example3
Copy link
Contributor

Choose a reason for hiding this comment

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

I personally think it would be useful to either expand this example to show the (compile-time) failure if you try to modify pi or leave this is an exercise so users can cause the error themselves.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Good point - I'll work on this.

theabro and others added 2 commits November 20, 2024 10:32
Co-authored-by: Warrick Ball <warrickball@gmail.com>
Co-authored-by: Warrick Ball <warrickball@gmail.com>
github-actions bot pushed a commit that referenced this pull request Nov 20, 2024
@theabro
Copy link
Collaborator Author

theabro commented Dec 2, 2024

I've now added the example error when trying to alter a parameter

github-actions bot pushed a commit that referenced this pull request Dec 2, 2024
@astroDimitrios astroDimitrios marked this pull request as draft March 17, 2025 15:41
github-actions bot pushed a commit that referenced this pull request Apr 17, 2025
github-actions bot pushed a commit that referenced this pull request Apr 23, 2025
github-actions bot pushed a commit that referenced this pull request Apr 25, 2025
github-actions bot pushed a commit that referenced this pull request Apr 25, 2025
github-actions bot pushed a commit that referenced this pull request Apr 25, 2025
github-actions bot pushed a commit that referenced this pull request Apr 25, 2025
github-actions bot pushed a commit that referenced this pull request Apr 25, 2025
github-actions bot pushed a commit that referenced this pull request Apr 25, 2025
github-actions bot pushed a commit that referenced this pull request Apr 29, 2025
github-actions bot pushed a commit that referenced this pull request May 19, 2025
@jklebes jklebes marked this pull request as ready for review September 11, 2025 12:03
Copy link
Collaborator

@jklebes jklebes left a comment

Choose a reason for hiding this comment

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

I tested building this as local webpage. I didn't test downloading the exercises or running the code examples.
Things were a bit confusing because of file 02-basiscs.Rmd, which is not displayed online and contains duplicate material. I made some duplicate comments. It looks like migration of content from Basics file to other files is unfinished, e.g. 05-strings is empty with the content in basics.
The content itself seems good and complete, with the minor comments. The formatting and writing is good.
I would finish the migration from 02-Basics and then merge PR, to change other details later.


1. Make sure your code conforms to the style
followed by this course.
2. Add Ford comments to document the program
Copy link
Collaborator

Choose a reason for hiding this comment

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

Has never been introduced


number_of_pelicans = 5
pelican_weight = 2.5 ! kg
pelican_population_dynamics = (-1.2e3, 0.9e2) ! births, deaths per year
Copy link
Collaborator

Choose a reason for hiding this comment

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

Unusual use of a complex number , maybe it's better to have no complex example here


| Relation | Operator | Older form | For |
|--------------------------|----------|------------|------------------|
| Less than | `< ` | `.lt.` | `integer` `real` |
Copy link
Collaborator

Choose a reason for hiding this comment

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

put commas in these lists in table

Equivalence between two logical expressions or variables is established
via the logical operators `.eqv.` and `.neqv.`.

While some some compilers may allow the use of `==`, this should be avoided.
Copy link
Collaborator

Choose a reason for hiding this comment

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

  • "to compare logical expression" - restate to be extra clear that this applies to logical and "==" should not be avoided in general.

T
```

## Character variables
Copy link
Collaborator

Choose a reason for hiding this comment

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

Draft content to be moved to file 05-strings ?


:::

::: caution
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think the big red warning box is a bit too attention-grabbing for this non-essential warning


1. Make sure your code conforms to the style
followed by this course.
2. Add Ford comments to document the program
Copy link
Collaborator

Choose a reason for hiding this comment

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

Has not been introduced

Equivalence between two logical expressions or variables is established
via the logical operators `.eqv.` and `.neqv.`.

While some some compilers may allow the use of `==`, this should be avoided.
Copy link
Collaborator

Choose a reason for hiding this comment

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

  • "when comparing logicals." , being explicit

```fortran
! This goes after the program statement
! We will cover modules in a later episode
use, intrinsic :: iso_fortran_env, only: r_32 => real32, r_64 => real64
Copy link
Collaborator

Choose a reason for hiding this comment

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

Should we just use the default names real32 to keep this use statement simple in number of new syntax/concepts to understand (and fitting on a line when displayed in browser)


:::::::::::::::::::::::::::::::::::::::: keypoints

- Th
Copy link
Collaborator

Choose a reason for hiding this comment

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

Unfinished

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants