TransportMaps.tests.test_kl_divergence

Module Contents

Classes

KL_divergence_DerivativeChecks
Serial_KL_divergence_DerivativeChecks
ParallelPool_KL_divergence_DerivativeChecks
Serial_PullBackTMD_KL_divergence_DerivativeChecks
ParallelPool_PullBackTMD_KL_divergence_DerivativeChecks
Serial_PushForwardTMD_KL_divergence_DerivativeChecks
ParallelPool_PushForwardTMD_KL_divergence_DerivativeChecks
IntegratedExponentialTM
Serial_IntegratedExponentialPBTMD_KL_divergence_DerivativeChecks
Serial_IntegratedExponentialPFTMD_KL_divergence_DerivativeChecks
ParallelPool_IntegratedExponentialPBTMD_KL_divergence_DerivativeChecks
ParallelPool_IntegratedExponentialPFTMD_KL_divergence_DerivativeChecks
IntegratedSquaredTM
Serial_IntegratedSquaredPBTMD_KL_divergence_DerivativeChecks
Serial_IntegratedSquaredPFTMD_KL_divergence_DerivativeChecks
ParallelPool_IntegratedSquaredPBTMD_KL_divergence_DerivativeChecks
ParallelPool_IntegratedSquaredPFTMD_KL_divergence_DerivativeChecks
TMD_TestCase
Linear1D_TMD_TestCase
ArcTan1D_TMD_TestCase
Exp1D_TMD_TestCase
Logistic1D_TMD_TestCase
Gamma1D_TMD_TestCase
Beta1D_TMD_TestCase
Gumbel1D_TMD_TestCase
Linear2D_TMD_TestCase
Banana2D_TMD_TestCase
Linear1D_Serial_IEPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
ArcTan1D_Serial_IEPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Exp1D_Serial_IEPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Logistic1D_Serial_IEPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Gamma1D_Serial_IEPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Beta1D_Serial_IEPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Gumbel1D_Serial_IEPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Linear2D_Serial_IEPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Banana2D_Serial_IEPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Linear1D_ParallelPool_IEPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
ArcTan1D_ParallelPool_IEPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Exp1D_ParallelPool_IEPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Logistic1D_ParallelPool_IEPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Gamma1D_ParallelPool_IEPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Beta1D_ParallelPool_IEPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Gumbel1D_ParallelPool_IEPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Linear2D_ParallelPool_IEPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Banana2D_ParallelPool_IEPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Linear1D_Serial_ISPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
ArcTan1D_Serial_ISPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Exp1D_Serial_ISPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Logistic1D_Serial_ISPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Gamma1D_Serial_ISPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Beta1D_Serial_ISPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Gumbel1D_Serial_ISPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Linear2D_Serial_ISPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Banana2D_Serial_ISPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Linear1D_ParallelPool_ISPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
ArcTan1D_ParallelPool_ISPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Exp1D_ParallelPool_ISPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Logistic1D_ParallelPool_ISPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Gamma1D_ParallelPool_ISPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Beta1D_ParallelPool_ISPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Gumbel1D_ParallelPool_ISPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Linear2D_ParallelPool_ISPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.
Banana2D_ParallelPool_ISPBTMD_KLdiv_DerivativeChecks	A class whose instances are single test cases.

Functions

build_suite([ttype])
run_tests([ttype, failfast])

class TransportMaps.tests.test_kl_divergence.KL_divergence_DerivativeChecks

Bases: object

setUp()

test_grad_a_kl_divergence()

test_tuple_grad_a_kl_divergence()

test_hess_a_kl_divergence()

test_action_storage_hess_a_kl_divergence()

test_action_hess_a_kl_divergence()

test_grad_x_grad_t_kl_divergence()

test_batch_grad_a_kl_divergence()

test_batch_tuple_grad_a_kl_divergence()

test_batch_hess_a_kl_divergence()

test_batch_action_storage_hess_a_kl_divergence()

test_batch_action_hess_a_kl_divergence()

test_precomp_grad_a_kl_divergence()

test_precomp_tuple_grad_a_kl_divergence()

test_precomp_hess_a_kl_divergence()

test_precomp_action_storage_hess_a_kl_divergence()

test_precomp_action_hess_a_kl_divergence()

test_precomp_batch_grad_a_kl_divergence()

test_precomp_batch_tuple_grad_a_kl_divergence()

test_precomp_batch_hess_a_kl_divergence()

test_precomp_batch_action_storage_hess_a_kl_divergence()

test_precomp_batch_action_hess_a_kl_divergence()

test_precomp_cached_grad_a_kl_divergence()

test_precomp_cached_tuple_grad_a_kl_divergence()

test_precomp_cached_hess_a_kl_divergence()

test_precomp_cached_action_storage_hess_a_kl_divergence()

test_precomp_cached_action_hess_a_kl_divergence()

test_precomp_cached_batch_grad_a_kl_divergence()

test_precomp_cached_batch_tuple_grad_a_kl_divergence()

test_precomp_cached_batch_hess_a_kl_divergence()

test_precomp_cached_batch_action_storage_hess_a_kl_divergence()

test_precomp_cached_batch_action_hess_a_kl_divergence()

class TransportMaps.tests.test_kl_divergence.Serial_KL_divergence_DerivativeChecks

Bases: KL_divergence_DerivativeChecks

setUp()

class TransportMaps.tests.test_kl_divergence.ParallelPool_KL_divergence_DerivativeChecks

Bases: KL_divergence_DerivativeChecks

setUp()

tearDown()

class TransportMaps.tests.test_kl_divergence.Serial_PullBackTMD_KL_divergence_DerivativeChecks

Bases: Serial_KL_divergence_DerivativeChecks

setUp()

class TransportMaps.tests.test_kl_divergence.ParallelPool_PullBackTMD_KL_divergence_DerivativeChecks

Bases: ParallelPool_KL_divergence_DerivativeChecks

setUp()

class TransportMaps.tests.test_kl_divergence.Serial_PushForwardTMD_KL_divergence_DerivativeChecks

Bases: Serial_KL_divergence_DerivativeChecks

setUp()

test_hess_a_kl_divergence()

test_batch_hess_a_kl_divergence()

test_action_hess_a_kl_divergence()

test_batch_action_hess_a_kl_divergence()

test_precomp_grad_a_kl_divergence()

test_precomp_hess_a_kl_divergence()

test_precomp_batch_grad_a_kl_divergence()

test_precomp_batch_hess_a_kl_divergence()

test_precomp_cached_grad_a_kl_divergence()

test_precomp_cached_hess_a_kl_divergence()

test_precomp_cached_batch_grad_a_kl_divergence()

test_precomp_cached_batch_hess_a_kl_divergence()

test_action_storage_hess_a_kl_divergence()

test_batch_action_storage_hess_a_kl_divergence()

test_precomp_action_storage_hess_a_kl_divergence()

test_precomp_batch_action_storage_hess_a_kl_divergence()

test_precomp_cached_action_storage_hess_a_kl_divergence()

test_precomp_cached_batch_action_storage_hess_a_kl_divergence()

test_cached_grad_a_kl_divergence()

class TransportMaps.tests.test_kl_divergence.ParallelPool_PushForwardTMD_KL_divergence_DerivativeChecks

Bases: ParallelPool_KL_divergence_DerivativeChecks

setUp()

test_hess_a_kl_divergence()

test_batch_hess_a_kl_divergence()

test_action_hess_a_kl_divergence()

test_batch_action_hess_a_kl_divergence()

test_precomp_grad_a_kl_divergence()

test_precomp_hess_a_kl_divergence()

test_precomp_batch_grad_a_kl_divergence()

test_precomp_batch_hess_a_kl_divergence()

test_precomp_cached_grad_a_kl_divergence()

test_precomp_cached_hess_a_kl_divergence()

test_precomp_cached_batch_grad_a_kl_divergence()

test_precomp_cached_batch_hess_a_kl_divergence()

test_action_storage_hess_a_kl_divergence()

test_batch_action_storage_hess_a_kl_divergence()

test_precomp_action_storage_hess_a_kl_divergence()

test_precomp_batch_action_storage_hess_a_kl_divergence()

test_precomp_cached_action_storage_hess_a_kl_divergence()

test_precomp_cached_batch_action_storage_hess_a_kl_divergence()

test_cached_grad_a_kl_divergence()

class TransportMaps.tests.test_kl_divergence.IntegratedExponentialTM

Bases: object

setUp_tm()

class TransportMaps.tests.test_kl_divergence.Serial_IntegratedExponentialPBTMD_KL_divergence_DerivativeChecks

Bases: IntegratedExponentialTM, Serial_PullBackTMD_KL_divergence_DerivativeChecks

setUp()

class TransportMaps.tests.test_kl_divergence.Serial_IntegratedExponentialPFTMD_KL_divergence_DerivativeChecks

Bases: IntegratedExponentialTM, Serial_PushForwardTMD_KL_divergence_DerivativeChecks

setUp()

class TransportMaps.tests.test_kl_divergence.ParallelPool_IntegratedExponentialPBTMD_KL_divergence_DerivativeChecks

Bases: IntegratedExponentialTM, ParallelPool_PullBackTMD_KL_divergence_DerivativeChecks

setUp()

class TransportMaps.tests.test_kl_divergence.ParallelPool_IntegratedExponentialPFTMD_KL_divergence_DerivativeChecks

Bases: IntegratedExponentialTM, ParallelPool_PushForwardTMD_KL_divergence_DerivativeChecks

setUp()

class TransportMaps.tests.test_kl_divergence.IntegratedSquaredTM

Bases: object

setUp_tm()

class TransportMaps.tests.test_kl_divergence.Serial_IntegratedSquaredPBTMD_KL_divergence_DerivativeChecks

Bases: IntegratedSquaredTM, Serial_PullBackTMD_KL_divergence_DerivativeChecks

setUp()

class TransportMaps.tests.test_kl_divergence.Serial_IntegratedSquaredPFTMD_KL_divergence_DerivativeChecks

Bases: IntegratedSquaredTM, Serial_PushForwardTMD_KL_divergence_DerivativeChecks

setUp()

class TransportMaps.tests.test_kl_divergence.ParallelPool_IntegratedSquaredPBTMD_KL_divergence_DerivativeChecks

Bases: IntegratedSquaredTM, ParallelPool_PullBackTMD_KL_divergence_DerivativeChecks

setUp()

class TransportMaps.tests.test_kl_divergence.ParallelPool_IntegratedSquaredPFTMD_KL_divergence_DerivativeChecks

Bases: IntegratedSquaredTM, ParallelPool_PushForwardTMD_KL_divergence_DerivativeChecks

setUp()

class TransportMaps.tests.test_kl_divergence.TMD_TestCase

Bases: object

_setUp_tcase()

class TransportMaps.tests.test_kl_divergence.Linear1D_TMD_TestCase

Bases: TMD_TestCase

_setUp_tcase()

class TransportMaps.tests.test_kl_divergence.ArcTan1D_TMD_TestCase

Bases: TMD_TestCase

_setUp_tcase()

class TransportMaps.tests.test_kl_divergence.Exp1D_TMD_TestCase

Bases: TMD_TestCase

_setUp_tcase()

class TransportMaps.tests.test_kl_divergence.Logistic1D_TMD_TestCase

Bases: TMD_TestCase

_setUp_tcase()

class TransportMaps.tests.test_kl_divergence.Gamma1D_TMD_TestCase

Bases: TMD_TestCase

_setUp_tcase()

class TransportMaps.tests.test_kl_divergence.Beta1D_TMD_TestCase

Bases: TMD_TestCase

_setUp_tcase()

class TransportMaps.tests.test_kl_divergence.Gumbel1D_TMD_TestCase

Bases: TMD_TestCase

_setUp_tcase()

class TransportMaps.tests.test_kl_divergence.Linear2D_TMD_TestCase

Bases: TMD_TestCase

_setUp_tcase()

class TransportMaps.tests.test_kl_divergence.Banana2D_TMD_TestCase

Bases: TMD_TestCase

_setUp_tcase()

class TransportMaps.tests.test_kl_divergence.Linear1D_Serial_IEPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Linear1D_TMD_TestCase, Serial_IntegratedExponentialPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.ArcTan1D_Serial_IEPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: ArcTan1D_TMD_TestCase, Serial_IntegratedExponentialPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Exp1D_Serial_IEPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Exp1D_TMD_TestCase, Serial_IntegratedExponentialPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Logistic1D_Serial_IEPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Logistic1D_TMD_TestCase, Serial_IntegratedExponentialPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Gamma1D_Serial_IEPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Gamma1D_TMD_TestCase, Serial_IntegratedExponentialPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Beta1D_Serial_IEPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Beta1D_TMD_TestCase, Serial_IntegratedExponentialPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Gumbel1D_Serial_IEPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Gumbel1D_TMD_TestCase, Serial_IntegratedExponentialPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Linear2D_Serial_IEPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Linear2D_TMD_TestCase, Serial_IntegratedExponentialPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Banana2D_Serial_IEPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Banana2D_TMD_TestCase, Serial_IntegratedExponentialPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Linear1D_ParallelPool_IEPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Linear1D_TMD_TestCase, ParallelPool_IntegratedExponentialPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.ArcTan1D_ParallelPool_IEPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: ArcTan1D_TMD_TestCase, ParallelPool_IntegratedExponentialPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Exp1D_ParallelPool_IEPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Exp1D_TMD_TestCase, ParallelPool_IntegratedExponentialPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Logistic1D_ParallelPool_IEPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Logistic1D_TMD_TestCase, ParallelPool_IntegratedExponentialPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Gamma1D_ParallelPool_IEPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Gamma1D_TMD_TestCase, ParallelPool_IntegratedExponentialPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Beta1D_ParallelPool_IEPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Beta1D_TMD_TestCase, ParallelPool_IntegratedExponentialPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Gumbel1D_ParallelPool_IEPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Gumbel1D_TMD_TestCase, ParallelPool_IntegratedExponentialPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Linear2D_ParallelPool_IEPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Linear2D_TMD_TestCase, ParallelPool_IntegratedExponentialPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Banana2D_ParallelPool_IEPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Banana2D_TMD_TestCase, ParallelPool_IntegratedExponentialPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Linear1D_Serial_ISPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Linear1D_TMD_TestCase, Serial_IntegratedSquaredPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.ArcTan1D_Serial_ISPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: ArcTan1D_TMD_TestCase, Serial_IntegratedSquaredPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Exp1D_Serial_ISPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Exp1D_TMD_TestCase, Serial_IntegratedSquaredPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Logistic1D_Serial_ISPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Logistic1D_TMD_TestCase, Serial_IntegratedSquaredPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Gamma1D_Serial_ISPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Gamma1D_TMD_TestCase, Serial_IntegratedSquaredPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Beta1D_Serial_ISPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Beta1D_TMD_TestCase, Serial_IntegratedSquaredPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Gumbel1D_Serial_ISPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Gumbel1D_TMD_TestCase, Serial_IntegratedSquaredPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Linear2D_Serial_ISPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Linear2D_TMD_TestCase, Serial_IntegratedSquaredPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Banana2D_Serial_ISPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Banana2D_TMD_TestCase, Serial_IntegratedSquaredPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Linear1D_ParallelPool_ISPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Linear1D_TMD_TestCase, ParallelPool_IntegratedSquaredPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.ArcTan1D_ParallelPool_ISPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: ArcTan1D_TMD_TestCase, ParallelPool_IntegratedSquaredPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Exp1D_ParallelPool_ISPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Exp1D_TMD_TestCase, ParallelPool_IntegratedSquaredPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Logistic1D_ParallelPool_ISPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Logistic1D_TMD_TestCase, ParallelPool_IntegratedSquaredPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Gamma1D_ParallelPool_ISPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Gamma1D_TMD_TestCase, ParallelPool_IntegratedSquaredPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Beta1D_ParallelPool_ISPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Beta1D_TMD_TestCase, ParallelPool_IntegratedSquaredPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Gumbel1D_ParallelPool_ISPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Gumbel1D_TMD_TestCase, ParallelPool_IntegratedSquaredPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Linear2D_ParallelPool_ISPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Linear2D_TMD_TestCase, ParallelPool_IntegratedSquaredPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_kl_divergence.Banana2D_ParallelPool_ISPBTMD_KLdiv_DerivativeChecks(methodName='runTest')

Bases: Banana2D_TMD_TestCase, ParallelPool_IntegratedSquaredPBTMD_KL_divergence_DerivativeChecks, unittest.TestCase

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named ‘runTest’.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.

If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when

the instance’s assertion methods fail; test methods raising this exception will be deemed to have ‘failed’ rather than ‘errored’.

• longMessage: determines whether long messages (including repr of

  objects used in assert methods) will be printed on failure in addition to any explicit message passed.

• maxDiff: sets the maximum length of a diff in failure messages

  by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

setUp()

Hook method for setting up the test fixture before exercising it.

TransportMaps.tests.test_kl_divergence.build_suite(ttype='all')

TransportMaps.tests.test_kl_divergence.run_tests(ttype='serial', failfast=False)