forked from OpenFAST/openfast
-
Notifications
You must be signed in to change notification settings - Fork 7
Add WaveTank module for wave tank test #28
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
Closed
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
was using log maps in the steady-state solver for differencing, but the perturbation function assumed they were angles when it adjusted them later
- set `NumPulseGate` and `NumBeam` consistently so we can cleanup some of the IF statement in the code - don't allow pulsed lidars to have 0 gates - remove unused lidar states - updated computation of `MsrPositionsY` and `MsrPositionsZ` for pulsed lidar. Previous calculations didn't make any sense to me
- move all lidar parameter initialization into lidar_init - remove unused lidar_initInput values and move the one that is used into InflowWind initInput - remove unused variables - check that lidar arrays are allocated before initializing them (before call to SrvD_Init and before reading from IfW file) - move logic to check number of beams allowed into lidar module and only make sure the value is at least 1 before allocating so beam focal distances can be read/parsed with valid arrays sizes - make ConsiderHubMotion an integer again since I don't want to change the input files
- remove unnecessary lidar allocatable arrays in SrvoDyn InitInp type - remove unused URefLid from ServoDyn InitInp; the value that is passed to the controller was never initialized and doesn't make sense for a controller to use anyway. - allocate lidar arrays for controller based on number of beams and pulse gates instead of type of lidar - initialize error status in BladedInterface_End routine
20.04 was deprecated last week on GH
Update GH conda-deploy action to use Ubuntu 24.04
Cleanup LIDAR code
bug fix: Adjust steady-state solver small angle assumptions
The C++ function declaration had an extra argument InflowType, that is not present in the Fortran function definition.
was using log maps in the steady-state solver for differencing, but the perturbation function assumed they were angles when it adjusted them later
MD: Backport of PR OpenFAST#2658
Fix FAST_ExtInfw_Restart API
backport of OpenFAST#2760: bug-fix: Adjust steady-state solver small angle assumptions
Backport of GitHub Action to build windows executables on release
When running from Simulink, Matlab would end (instead of the DLL). This PR fixes the problem.
Avoid ending program when called as a shared library
Docs: update info on testing
VS build: fix MD, add `SeaStateS_c_binding` and update GH `deploy` action
…es_4.1.0 Release notes and version updates for 4.1.0
Added info on code API changes
Missing PR OpenFAST#2650
- Include mention of VIV in MD - Mention why SuperController has been depricated (in favor of ZeroMQ communication through ROSCO) - Include links to MD input file info for SeaState coupling and VIV
Add space for clarity Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
GH actions - fix paths and change to artifacts instead of cache so `requirements.txt` is reliably found
# Conflicts: # modules/aerodyn/src/AeroDyn_Inflow.f90 # modules/aerodyn/src/AeroDyn_Inflow_C_Binding.f90
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add WaveTank module for wave tank test
This pull request primarily focuses on the development of a module for driving a wave tank experimental setup coupling AeroDyn, InflowWind, MoorDyn, and SeaState to model the loads due to waves and current on a MHK turbine floating structure. To that end, the primary addition is the
WaveTankmodule in theglue-codes/labviewdirectory since it is driven by the LabVIEW experiment setup.This pull request depends on OpenFAST#2735.
Note: In order to properly view the files changes, this PR is currently targeting rafmudaf/dev-cbind-wavetank. After OpenFAST#2735 is merged, I will update this pull request to target the appropriate branch on the OpenFAST/openfast repository.