README.md File Reference

Functions/Subroutines

http including the
Interoperable Physics 
Driver (IPD).[![Build Status](https
if please open an issue The
output should be similar tests
failed out of Total Test 
time (real)=0.08 sec```A suite is defined in XML.There is a test suite definied within the`tests`directory
if please open an issue The
output should be similar tests
failed out of Total Test there
is also the XML Schema
Definition in that directory
too To validate a new test you
can use xmllint For example to
validate suite_RAP the dummy
scheme has a cap called
dummy_cap The requirements are
that it is Lowercased _cap is
appended b Map all the inputs
for the cap from the cdata
encapsulating 
type (this is of the`ccpp_t`type).The cap will extract the fields from the fields array with the`ccpp_fields_get()`subroutine.An example of a scheme that does nothing is`schemes/check/test.f90`.The CCPP must first be initialized
if please open an issue The
output should be similar tests
failed out of Total Test there
is also the XML Schema
Definition in that directory
too To validate a new test you
can use xmllint For example to
validate suite_RAP the dummy
scheme has a cap called
dummy_cap The requirements are
that it is Lowercased _cap is
appended b Map all the inputs
for the cap from the cdata
encapsulating this is done by
calling ccpp 
_init ()`.Once initialized
if please open an issue The
output should be similar tests
failed out of Total Test there
is also the XML Schema
Definition in that directory
too To validate a new test you
can use xmllint For example to
validate suite_RAP the dummy
scheme has a cap called
dummy_cap The requirements are
that it is Lowercased _cap is
appended b Map all the inputs
for the cap from the cdata
encapsulating this is done by
calling ccpp all variables
that will be required in a
physics scheme have to be
added to the ccpp data 
object (of type`ccpp_t`).These variables can later be retrieved in a physics schemes cap.Example usage

Variables

http __pad0__
 __pad1__
if not
if please open an issue The
output should be similar 
to
if please open an issue The
output should be similar tests
failed out of Total Test there
is also the XML Schema
Definition in that directory
too To validate a new test 
suite
if please open an issue The
output should be similar tests
failed out of Total Test there
is also the XML Schema
Definition in that directory
too To validate a new test you
can use xmllint For example to
validate suite_RAP 
xml
if please open an issue The
output should be similar tests
failed out of Total Test there
is also the XML Schema
Definition in that directory
too To validate a new test you
can use xmllint For example to
validate suite_RAP the dummy
scheme has a cap called
dummy_cap The requirements are
that it is Lowercased _cap is
appended b Map all the inputs
for the cap from the cdata
encapsulating this is done by
calling ccpp all variables
that will be required in a
physics scheme have to be
added to the ccpp data in an
atmosphere 
component

Function Documentation

if please open an issue The output should be similar tests failed out of Total Test there is also the XML Schema Definition in that directory too To validate a new test you can use xmllint For example to validate suite_RAP the dummy scheme has a cap called dummy_cap The requirements are that it is Lowercased _cap is appended b Map all the inputs for the cap from the cdata encapsulating this is done by calling ccpp _init (  ) 
http including the Interoperable Physics Driver ( IPD   ) 
Type Constraints
if please open an issue The output should be similar tests failed out of Total Test there is also the XML Schema Definition in that directory too To validate a new test you can use xmllint For example to validate suite_RAP the dummy scheme has a cap called dummy_cap The requirements are that it is Lowercased _cap is appended b Map all the inputs for the cap from the cdata encapsulating this is done by calling ccpp all variables that will be required in a physics scheme have to be added to the ccpp data object ( of type`ccpp_t`   ) 
if please open an issue The output should be similar tests failed out of Total Test time ( real   )  [pure virtual]
Type Constraints
if please open an issue The output should be similar tests failed out of Total Test there is also the XML Schema Definition in that directory too To validate a new test you can use xmllint For example to validate suite_RAP the dummy scheme has a cap called dummy_cap The requirements are that it is Lowercased _cap is appended b Map all the inputs for the cap from the cdata encapsulating type ( this is of the`ccpp_t`  type  ) 
Type Constraints

Variable Documentation

http __pad0__
if please open an issue The output should be similar tests failed out of Total Test there is also the XML Schema Definition in that directory too To validate a new test you can use xmllint For example to validate suite_RAP the dummy scheme has a cap called dummy_cap The requirements are that it is Lowercased _cap is appended b Map all the inputs for the cap from the cdata encapsulating this is done by calling ccpp all variables that will be required in a physics scheme have to be added to the ccpp data in an atmosphere component
if not
if please open an issue The output should be similar tests failed out of Total Test there is also the XML Schema Definition in that directory too To validate a new test suite
if please open an issue The output should be similar to
if please open an issue The output should be similar tests failed out of Total Test there is also the XML Schema Definition in that directory too To validate a new test you can use xmllint For example to validate suite_RAP xml
 All Classes Namespaces Files Functions Variables Defines

Generated on 26 Apr 2017 for ccpp by  doxygen 1.6.1