Skip to content
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

Fortran standard to 2008 #53

Merged
merged 19 commits into from
Aug 3, 2021
Merged

Fortran standard to 2008 #53

merged 19 commits into from
Aug 3, 2021

Conversation

gawng
Copy link
Contributor

@gawng gawng commented Jul 12, 2021

Purpose

The Fortran standard is 2008 because petsc wasn't cooperating with earlier standards.

Type of change

What types of change is it?
Select the appropriate type(s) that describe this PR

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (non-backwards-compatible fix or feature)
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no API changes)
  • Documentation update
  • Maintenance update
  • Other (please describe)

Testing

I do not have complex IDWarp compiled, so those tests were skipped.

Checklist

Put an x in the boxes that apply.

  • I have run flake8 and black to make sure the code adheres to PEP-8 and is consistently formatted
  • I have run unit and regression tests which pass locally with my changes
  • I have added new tests that prove my fix is effective or that my feature works
  • I have added necessary documentation

@gawng gawng requested a review from a team as a code owner July 12, 2021 18:38
@gawng gawng requested review from SichengHe and joanibal July 12, 2021 18:38
Copy link
Contributor

@marcomangano marcomangano left a comment

Choose a reason for hiding this comment

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

Can you confirm these changes are intentional?

marcomangano
marcomangano previously approved these changes Jul 13, 2021
@ewu63
Copy link
Collaborator

ewu63 commented Jul 13, 2021

I'm not 100% convinced we want to manually update the ADFirstAidKit stuff. A couple options here:

  • do what's currently done in the PR, and then submit a patch upstream
  • fix this here, but then refactor and move into a separate package (since multiple repos use the same code)
  • modify the rules so we don't apply new Fortran standard here

Let's talk about this during the next maintenance meeting maybe.

@codecov
Copy link

codecov bot commented Jul 19, 2021

Codecov Report

Merging #53 (e911a6b) into master (136b3bb) will decrease coverage by 0.06%.
The diff coverage is n/a.

❗ Current head e911a6b differs from pull request most recent head f43c669. Consider uploading reports for the commit f43c669 to get more accurate results
Impacted file tree graph

@@            Coverage Diff             @@
##           master      #53      +/-   ##
==========================================
- Coverage   46.13%   46.06%   -0.07%     
==========================================
  Files           6        6              
  Lines         776      775       -1     
==========================================
- Hits          358      357       -1     
  Misses        418      418              
Impacted Files Coverage Δ
idwarp/MExt.py 97.36% <0.00%> (-0.07%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 136b3bb...f43c669. Read the comment docs.

@ewu63
Copy link
Collaborator

ewu63 commented Jul 19, 2021

How does this look @eirikurj @bernardopacini? I added a new flag for F77 code which omits the standard specification. The flags can probably be simplified (we probably don't need PETSc/CGNS since it's just the Tapenade code).

I also see that @gang525 updated the complexify module. I assume this is unavoidable since we do not have a centralized complexify package (yet) and this is OK here. We will of course have to do the same thing for other repos that use the same module (but potentially have slightly different code).

@ewu63 ewu63 requested a review from eirikurj July 23, 2021 12:44
eirikurj
eirikurj previously approved these changes Aug 3, 2021
Copy link
Contributor

@eirikurj eirikurj left a comment

Choose a reason for hiding this comment

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

Overall, this looks good. I got some feedback from the Tapenade people and according to them, future version of Tapenade will not include the .f files, only the C files, so eventually we could remove the F77 rules. For the time being, we can just keep this as is.

@ewu63 ewu63 requested a review from marcomangano August 3, 2021 18:23
Copy link
Contributor

@marcomangano marcomangano left a comment

Choose a reason for hiding this comment

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

Up for the tapenade checks addition

@ewu63 ewu63 merged commit 1139b7d into mdolab:master Aug 3, 2021
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