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

Compilation error on dev branch #24

Closed
sayerhs opened this issue May 7, 2017 · 4 comments
Closed

Compilation error on dev branch #24

sayerhs opened this issue May 7, 2017 · 4 comments
Assignees

Comments

@sayerhs
Copy link
Contributor

sayerhs commented May 7, 2017

With the latest updates on the dev branch, I get a compilation error when using GNU gfortran 6.3.0. I am not sure where the character length 11 is showing up, every entry in ParamUnitsAry is neatly formatted and looks like it is 10 characters long.

openfast/modules-local/aerodyn/src/AeroDyn_IO.f90:3092:122:

                                "(N/m)     ","(N/m)     ","(N/m)     ","(N/m)     ","(N/m)     ","(N/m)     ","(-)       ", &
                                                                                                                          1
Error: Different CHARACTER lengths (10/11) in array constructor at (1)
openfast/modules-local/aerodyn/src/AeroDyn_IO.f90:3446:34:

             p%OutParam(I)%Units = ParamUnitsAry(Indx) ! it's a valid output
                                  1
Error: Function 'paramunitsary' at (1) has no IMPLICIT type

@ghaymanNREL @bjonkman

@HaymanConsulting
Copy link
Contributor

HaymanConsulting commented May 8, 2017 via email

@sayerhs
Copy link
Contributor Author

sayerhs commented May 8, 2017

@ghaymanNREL I wonder if this is an ASCII/Unicode issue. One of those characters might be encoded as 2 characters if the file is interpreted as pure ASCII but it has unicode characters.

@sayerhs
Copy link
Contributor Author

sayerhs commented May 8, 2017

Commit b8ea3c2 fixes the issue on GNU gfortran v6.3.0.

@sayerhs sayerhs closed this as completed May 8, 2017
@bjonkman
Copy link
Contributor

bjonkman commented May 8, 2017

FYI, those units arrays often contain extended ASCII characters, and I have noticed that GitKracken has a tendency to convert them to unicode if you use it to make other changes to the source file.

This was referenced Mar 23, 2022
psakievich pushed a commit to psakievich/openfast that referenced this issue Aug 4, 2023
Make netcdf output parallel consistent
andrew-platt added a commit that referenced this issue Jul 8, 2024
Add intertialF_rampT as input option
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants