Intel config

[hajdik]

Purpose

The intel config didn't work on Pleiades so I added the switch in the IDWarp intel config which did successfully build on the cluster and relevant pyGeo tests passed. I didn't refactor the rest of the config as it does work but if there are best practices to follow I can do so.

Also edited some Python files to address Black rules that are new since the last GeoGrad PR.

Expected time until merged

No rush

Type of change

• 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

Config runs on intel images

Checklist

• I have run flake8 and black to make sure the Python code adheres to PEP-8 and is consistently formatted
• I have formatted the Fortran code with fprettify or C/C++ code with clang-format as applicable
• 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

[sseraj]

Following other best practices would be a much larger effort and would probably involve restructuring the repo a bit. I opened #15 to track some updates that should be made eventually.

This looks fine other than the Python formatting and my one comment below.

[eirikurj]

bump @hajdik

[eirikurj]

bump @hajdik

[hajdik]

I addressed @sseraj's comment and fixed the black check. I'll address the broader restructuring in #15 soon.

[eirikurj]

@hajdik changes are fine, but I think we should add support for the new intel compiler. See idwarp for reference. Can you add this? We can also add this in a separate PR.