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

The doxygen comments have been added for all files. #3

Merged
merged 1 commit into from
Apr 23, 2020
Merged

Conversation

TakisCFD
Copy link
Collaborator

Fixed a few compiling issues with gfortran.
Fixed a bug in dual time stepping loop counter.

Fixed a few compiling issues with gfortran.
Fixed a bug in dual time stepping loop counter.
@TakisCFD TakisCFD requested a review from Antonis-F April 23, 2020 09:11
@TakisCFD TakisCFD merged commit d39427f into master Apr 23, 2020
Copy link
Collaborator

@Antonis-F Antonis-F left a comment

Choose a reason for hiding this comment

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

Looks Good to Me

general suggestion would be to make pull request as atomic/minimal as possible i.e. one thing ffeature / bug etc rather several ones 😸

F90=mpiifort

Copy link
Collaborator

Choose a reason for hiding this comment

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

nice, what about passing the option of type of compiler through as argument
i.e. intel, gcc etc
see here
https://stackoverflow.com/a/2826178/4679900

Copy link
Collaborator

Choose a reason for hiding this comment

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

i guess eventually would be nice to have a separate config step and then we do make all or something 😄

if (ielem(n,i)%interior.eq.1)then !THAT HAVE AT LEAST ONE UNKNWON NEIGHBOUR
IF (ielem(n,i)%nofbc.GT.0)THEN !THAT HAVE AT LEAST ESTABLISHED A BOUNDARY CONDITION CODE
DO J=1,ielem(n,i)%IFCA !LOOP ALL THEIR BOUNDARY FACES
DO I=1,KMAXE !> ALL ELEMENTS
Copy link
Collaborator

Choose a reason for hiding this comment

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

is doxygen convention to have inline comments rather than top of the function/subroutine ?

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.

None yet

2 participants