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

All driver use statements should be to marbl_interface* #83

Open
mnlevy1981 opened this issue Jun 30, 2016 · 0 comments
Open

All driver use statements should be to marbl_interface* #83

mnlevy1981 opened this issue Jun 30, 2016 · 0 comments
Milestone

Comments

@mnlevy1981
Copy link
Collaborator

The stand-alone driver currently requires the following from libmarbl.a

  use marbl_interface,    only : marbl_interface_class
  use marbl_logging,      only : marbl_log_type
  use marbl_logging,      only : marbl_status_log_entry_type
  use marbl_namelist_mod, only : marbl_nl_in_size
  use marbl_namelist_mod, only : marbl_nl_cnt
  use marbl_namelist_mod, only : marbl_nl_buffer_size
  use marbl_namelist_mod, only : marbl_nl_split_string
  use marbl_namelist_mod, only : marbl_namelist

and

  use marbl_kinds_mod,     only : r8
  use marbl_constants_mod, only : c1, p5

I think we want all these variables to come via marbl_interface / marbl_interface_types (and maybe the last two via marbl_interface_constants). The easiest solution would be to leave them where they are, but add use statements in marbl_interface*.F90 and make the above variables public in that module.

@mnlevy1981 mnlevy1981 added this to the Finalize MARBL API milestone Jun 30, 2016
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

No branches or pull requests

1 participant