`TransportMaps.tests.test_transportmap_distributions_sampling`¶

Module Contents¶

Classes¶

`TransportMapDistribution_SamplingCheck`
`PullBackTMD_SamplingCheck`
`PushForwardTMD_SamplingCheck`
`Serial_PBTMD_SamplingCheck`
`Serial_PFTMD_SamplingCheck`
`Parallel_PBTMD_SamplingCheck`
`Parallel_PFTMD_SamplingCheck`
`IntegratedExponential`
`Serial_IntegratedExponentialPBTMD_SamplingCheck`
`Serial_IntegratedExponentialPFTMD_SamplingCheck`
`Parallel_IntegratedExponentialPBTMD_SamplingCheck`
`Parallel_IntegratedExponentialPFTMD_SamplingCheck`
`CommonBasisIntegratedExponential`
`Serial_CommonBasisIntegratedExponentialPBTMD_SamplingCheck`
`Serial_CommonBasisIntegratedExponentialPFTMD_SamplingCheck`
`Parallel_CommonBasisIntegratedExponentialPBTMD_SamplingCheck`
`Parallel_CommonBasisIntegratedExponentialPFTMD_SamplingCheck`
`TotOrdIntegratedExponential`
`Serial_TotOrdIntegratedExponentialPBTMD_SamplingCheck`
`Serial_TotOrdIntegratedExponentialPFTMD_SamplingCheck`
`Parallel_TotOrdIntegratedExponentialPBTMD_SamplingCheck`
`Parallel_TotOrdIntegratedExponentialPFTMD_SamplingCheck`
`CommonBasisTotOrdIntegratedExponential`
`Serial_CommonBasisTotOrdIntegratedExponentialPBTMD_SamplingCheck`
`Serial_CommonBasisTotOrdIntegratedExponentialPFTMD_SamplingCheck`
`Parallel_CommonBasisTotOrdIntegratedExponentialPBTMD_SamplingCheck`
`Parallel_CommonBasisTotOrdIntegratedExponentialPFTMD_SamplingCheck`
`IntegratedSquared`
`Serial_IntegratedSquaredPBTMD_SamplingCheck`
`Serial_IntegratedSquaredPFTMD_SamplingCheck`
`Parallel_IntegratedSquaredPBTMD_SamplingCheck`
`Parallel_IntegratedSquaredPFTMD_SamplingCheck`
`CommonBasisIntegratedSquared`
`Serial_CommonBasisIntegratedSquaredPBTMD_SamplingCheck`
`Serial_CommonBasisIntegratedSquaredPFTMD_SamplingCheck`
`Parallel_CommonBasisIntegratedSquaredPBTMD_SamplingCheck`
`Parallel_CommonBasisIntegratedSquaredPFTMD_SamplingCheck`
`TotOrdIntegratedSquared`
`Serial_TotOrdIntegratedSquaredPBTMD_SamplingCheck`
`Serial_TotOrdIntegratedSquaredPFTMD_SamplingCheck`
`Parallel_TotOrdIntegratedSquaredPBTMD_SamplingCheck`
`Parallel_TotOrdIntegratedSquaredPFTMD_SamplingCheck`
`CommonBasisTotOrdIntegratedSquared`
`Serial_CommonBasisTotOrdIntegratedSquaredPBTMD_SamplingCheck`
`Serial_CommonBasisTotOrdIntegratedSquaredPFTMD_SamplingCheck`
`Parallel_CommonBasisTotOrdIntegratedSquaredPBTMD_SamplingCheck`
`Parallel_CommonBasisTotOrdIntegratedSquaredPFTMD_SamplingCheck`
`Serial_LinearSpanPBTMD_SamplingCheck`
`Serial_CommonBasisLinearSpanPBTMD_SamplingCheck`
`Parallel_LinearSpanPBTMD_SamplingCheck`
`Parallel_CommonBasisLinearSpanPBTMD_SamplingCheck`
`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`
`Serial_Linear1D_IEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_ArcTan1D_IEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Exp1D_IEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Logistic1D_IEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Gamma1D_IEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Beta1D_IEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Gumbel1D_IEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Linear2D_IEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Banana2D_IEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Linear1D_CBIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_ArcTan1D_CBIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Exp1D_CBIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Logistic1D_CBIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Gamma1D_CBIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Beta1D_CBIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Gumbel1D_CBIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Linear2D_CBIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Banana2D_CBIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Linear1D_TOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_ArcTan1D_TOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Exp1D_TOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Logistic1D_TOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Gamma1D_TOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Beta1D_TOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Gumbel1D_TOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Linear2D_TOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Banana2D_TOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Linear1D_CBTOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_ArcTan1D_CBTOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Exp1D_CBTOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Logistic1D_CBTOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Gamma1D_CBTOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Beta1D_CBTOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Gumbel1D_CBTOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Linear2D_CBTOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Banana2D_CBTOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Linear1D_IEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_ArcTan1D_IEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Exp1D_IEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Logistic1D_IEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Gamma1D_IEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Beta1D_IEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Gumbel1D_IEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Linear2D_IEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Banana2D_IEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Linear1D_CBIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_ArcTan1D_CBIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Exp1D_CBIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Logistic1D_CBIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Gamma1D_CBIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Beta1D_CBIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Gumbel1D_CBIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Linear2D_CBIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Banana2D_CBIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Linear1D_TOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_ArcTan1D_TOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Exp1D_TOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Logistic1D_TOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Gamma1D_TOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Beta1D_TOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Gumbel1D_TOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Linear2D_TOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Banana2D_TOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Linear1D_CBTOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_ArcTan1D_CBTOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Exp1D_CBTOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Logistic1D_CBTOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Gamma1D_CBTOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Beta1D_CBTOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Gumbel1D_CBTOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Linear2D_CBTOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Banana2D_CBTOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Linear1D_ISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_ArcTan1D_ISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Exp1D_ISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Logistic1D_ISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Gamma1D_ISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Beta1D_ISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Gumbel1D_ISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Linear2D_ISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Banana2D_ISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Linear1D_TOISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_ArcTan1D_TOISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Exp1D_TOISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Logistic1D_TOISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Gamma1D_TOISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Beta1D_TOISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Gumbel1D_TOISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Linear2D_TOISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Banana2D_TOISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Linear1D_ISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_ArcTan1D_ISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Exp1D_ISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Logistic1D_ISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Gamma1D_ISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Beta1D_ISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Gumbel1D_ISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Linear2D_ISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Banana2D_ISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Linear1D_TOISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_ArcTan1D_TOISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Exp1D_TOISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Logistic1D_TOISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Gamma1D_TOISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Beta1D_TOISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Gumbel1D_TOISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Linear2D_TOISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Banana2D_TOISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Linear1D_LSPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Serial_Linear1D_CBLSPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Linear1D_IEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_ArcTan1D_IEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Exp1D_IEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Logistic1D_IEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Gamma1D_IEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Beta1D_IEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Gumbel1D_IEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Linear2D_IEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Banana2D_IEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Linear1D_CBIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_ArcTan1D_CBIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Exp1D_CBIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Logistic1D_CBIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Gamma1D_CBIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Beta1D_CBIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Gumbel1D_CBIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Linear2D_CBIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Banana2D_CBIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Linear1D_TOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_ArcTan1D_TOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Exp1D_TOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Logistic1D_TOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Gamma1D_TOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Beta1D_TOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Gumbel1D_TOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Linear2D_TOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Banana2D_TOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Linear1D_CBTOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_ArcTan1D_CBTOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Exp1D_CBTOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Logistic1D_CBTOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Gamma1D_CBTOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Beta1D_CBTOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Gumbel1D_CBTOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Linear2D_CBTOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Banana2D_CBTOIEPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Linear1D_IEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_ArcTan1D_IEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Exp1D_IEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Logistic1D_IEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Gamma1D_IEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Beta1D_IEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Gumbel1D_IEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Linear2D_IEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Banana2D_IEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Linear1D_CBIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_ArcTan1D_CBIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Exp1D_CBIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Logistic1D_CBIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Gamma1D_CBIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Beta1D_CBIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Gumbel1D_CBIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Linear2D_CBIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Banana2D_CBIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Linear1D_TOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_ArcTan1D_TOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Exp1D_TOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Logistic1D_TOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Gamma1D_TOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Beta1D_TOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Gumbel1D_TOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Linear2D_TOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Banana2D_TOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Linear1D_CBTOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_ArcTan1D_CBTOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Exp1D_CBTOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Logistic1D_CBTOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Gamma1D_CBTOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Beta1D_CBTOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Gumbel1D_CBTOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Linear2D_CBTOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Banana2D_CBTOIEPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Linear1D_ISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_ArcTan1D_ISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Exp1D_ISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Logistic1D_ISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Gamma1D_ISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Beta1D_ISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Gumbel1D_ISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Linear2D_ISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Banana2D_ISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Linear1D_TOISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_ArcTan1D_TOISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Exp1D_TOISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Logistic1D_TOISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Gamma1D_TOISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Beta1D_TOISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Gumbel1D_TOISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Linear2D_TOISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Banana2D_TOISPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Linear1D_ISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_ArcTan1D_ISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Exp1D_ISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Logistic1D_ISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Gamma1D_ISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Beta1D_ISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Gumbel1D_ISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Linear2D_ISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Banana2D_ISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Linear1D_TOISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_ArcTan1D_TOISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Exp1D_TOISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Logistic1D_TOISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Gamma1D_TOISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Beta1D_TOISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Gumbel1D_TOISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Linear2D_TOISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Banana2D_TOISPFTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Linear1D_LSPBTMD_SamplingCheck`	A class whose instances are single test cases.
`Parallel_Linear1D_CBLSPBTMD_SamplingCheck`	A class whose instances are single test cases.

Functions¶

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

class TransportMaps.tests.test_transportmap_distributions_sampling.TransportMapDistribution_SamplingCheck[source]¶

Bases: object

setUp()[source]¶

test_rvs()[source]¶

test_quadrature()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.PullBackTMD_SamplingCheck[source]¶

Bases: TransportMapDistribution_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.PushForwardTMD_SamplingCheck[source]¶

Bases: TransportMapDistribution_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_PBTMD_SamplingCheck[source]¶

Bases: PullBackTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_PFTMD_SamplingCheck[source]¶

Bases: PushForwardTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_PBTMD_SamplingCheck[source]¶

Bases: PullBackTMD_SamplingCheck

setUp()[source]¶

tearDown()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_PFTMD_SamplingCheck[source]¶

Bases: PushForwardTMD_SamplingCheck

setUp()[source]¶

tearDown()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.IntegratedExponential[source]¶

setUpApprox()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_IntegratedExponentialPBTMD_SamplingCheck[source]¶

Bases: IntegratedExponential, Serial_PBTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_IntegratedExponentialPFTMD_SamplingCheck[source]¶

Bases: IntegratedExponential, Serial_PFTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_IntegratedExponentialPBTMD_SamplingCheck[source]¶

Bases: IntegratedExponential, Parallel_PBTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_IntegratedExponentialPFTMD_SamplingCheck[source]¶

Bases: IntegratedExponential, Parallel_PFTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.CommonBasisIntegratedExponential[source]¶

setUpApprox()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_CommonBasisIntegratedExponentialPBTMD_SamplingCheck[source]¶

Bases: CommonBasisIntegratedExponential, Serial_PBTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_CommonBasisIntegratedExponentialPFTMD_SamplingCheck[source]¶

Bases: CommonBasisIntegratedExponential, Serial_PFTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_CommonBasisIntegratedExponentialPBTMD_SamplingCheck[source]¶

Bases: CommonBasisIntegratedExponential, Parallel_PBTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_CommonBasisIntegratedExponentialPFTMD_SamplingCheck[source]¶

Bases: CommonBasisIntegratedExponential, Parallel_PFTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.TotOrdIntegratedExponential[source]¶

setUpApprox()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_TotOrdIntegratedExponentialPBTMD_SamplingCheck[source]¶

Bases: TotOrdIntegratedExponential, Serial_PBTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_TotOrdIntegratedExponentialPFTMD_SamplingCheck[source]¶

Bases: TotOrdIntegratedExponential, Serial_PFTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_TotOrdIntegratedExponentialPBTMD_SamplingCheck[source]¶

Bases: TotOrdIntegratedExponential, Parallel_PBTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_TotOrdIntegratedExponentialPFTMD_SamplingCheck[source]¶

Bases: TotOrdIntegratedExponential, Parallel_PFTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.CommonBasisTotOrdIntegratedExponential[source]¶

setUpApprox()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_CommonBasisTotOrdIntegratedExponentialPBTMD_SamplingCheck[source]¶

Bases: CommonBasisTotOrdIntegratedExponential, Serial_PBTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_CommonBasisTotOrdIntegratedExponentialPFTMD_SamplingCheck[source]¶

Bases: CommonBasisTotOrdIntegratedExponential, Serial_PFTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_CommonBasisTotOrdIntegratedExponentialPBTMD_SamplingCheck[source]¶

Bases: CommonBasisTotOrdIntegratedExponential, Parallel_PBTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_CommonBasisTotOrdIntegratedExponentialPFTMD_SamplingCheck[source]¶

Bases: CommonBasisTotOrdIntegratedExponential, Parallel_PFTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.IntegratedSquared[source]¶

setUpApprox()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_IntegratedSquaredPBTMD_SamplingCheck[source]¶

Bases: IntegratedSquared, Serial_PBTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_IntegratedSquaredPFTMD_SamplingCheck[source]¶

Bases: IntegratedSquared, Serial_PFTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_IntegratedSquaredPBTMD_SamplingCheck[source]¶

Bases: IntegratedSquared, Parallel_PBTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_IntegratedSquaredPFTMD_SamplingCheck[source]¶

Bases: IntegratedSquared, Parallel_PFTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.CommonBasisIntegratedSquared[source]¶

setUpApprox()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_CommonBasisIntegratedSquaredPBTMD_SamplingCheck[source]¶

Bases: CommonBasisIntegratedSquared, Serial_PBTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_CommonBasisIntegratedSquaredPFTMD_SamplingCheck[source]¶

Bases: CommonBasisIntegratedSquared, Serial_PFTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_CommonBasisIntegratedSquaredPBTMD_SamplingCheck[source]¶

Bases: CommonBasisIntegratedSquared, Parallel_PBTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_CommonBasisIntegratedSquaredPFTMD_SamplingCheck[source]¶

Bases: CommonBasisIntegratedSquared, Parallel_PFTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.TotOrdIntegratedSquared[source]¶

setUpApprox()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_TotOrdIntegratedSquaredPBTMD_SamplingCheck[source]¶

Bases: TotOrdIntegratedSquared, Serial_PBTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_TotOrdIntegratedSquaredPFTMD_SamplingCheck[source]¶

Bases: TotOrdIntegratedSquared, Serial_PFTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_TotOrdIntegratedSquaredPBTMD_SamplingCheck[source]¶

Bases: TotOrdIntegratedSquared, Parallel_PBTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_TotOrdIntegratedSquaredPFTMD_SamplingCheck[source]¶

Bases: TotOrdIntegratedSquared, Parallel_PFTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.CommonBasisTotOrdIntegratedSquared[source]¶

setUpApprox()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_CommonBasisTotOrdIntegratedSquaredPBTMD_SamplingCheck[source]¶

Bases: CommonBasisTotOrdIntegratedSquared, Serial_PBTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_CommonBasisTotOrdIntegratedSquaredPFTMD_SamplingCheck[source]¶

Bases: CommonBasisTotOrdIntegratedSquared, Serial_PFTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_CommonBasisTotOrdIntegratedSquaredPBTMD_SamplingCheck[source]¶

Bases: CommonBasisTotOrdIntegratedSquared, Parallel_PBTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_CommonBasisTotOrdIntegratedSquaredPFTMD_SamplingCheck[source]¶

Bases: CommonBasisTotOrdIntegratedSquared, Parallel_PFTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_LinearSpanPBTMD_SamplingCheck[source]¶

Bases: Serial_PBTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_CommonBasisLinearSpanPBTMD_SamplingCheck[source]¶

Bases: Serial_PBTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_LinearSpanPBTMD_SamplingCheck[source]¶

Bases: Parallel_PBTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_CommonBasisLinearSpanPBTMD_SamplingCheck[source]¶

Bases: Parallel_PBTMD_SamplingCheck

setUp()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.TMD_TestCase[source]¶

Bases: object

_setUp_tcase()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Linear1D_TMD_TestCase[source]¶

Bases: TMD_TestCase

_setUp_tcase()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.ArcTan1D_TMD_TestCase[source]¶

Bases: TMD_TestCase

_setUp_tcase()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Exp1D_TMD_TestCase[source]¶

Bases: TMD_TestCase

_setUp_tcase()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Logistic1D_TMD_TestCase[source]¶

Bases: TMD_TestCase

_setUp_tcase()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Gamma1D_TMD_TestCase[source]¶

Bases: TMD_TestCase

_setUp_tcase()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Beta1D_TMD_TestCase[source]¶

Bases: TMD_TestCase

_setUp_tcase()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Gumbel1D_TMD_TestCase[source]¶

Bases: TMD_TestCase

_setUp_tcase()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Linear2D_TMD_TestCase[source]¶

Bases: TMD_TestCase

_setUp_tcase()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Banana2D_TMD_TestCase[source]¶

Bases: TMD_TestCase

_setUp_tcase()[source]¶

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Linear1D_IEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear1D_TMD_TestCase, Serial_IntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_ArcTan1D_IEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: ArcTan1D_TMD_TestCase, Serial_IntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Exp1D_IEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Exp1D_TMD_TestCase, Serial_IntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Logistic1D_IEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Logistic1D_TMD_TestCase, Serial_IntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Gamma1D_IEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gamma1D_TMD_TestCase, Serial_IntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Beta1D_IEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Beta1D_TMD_TestCase, Serial_IntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Gumbel1D_IEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gumbel1D_TMD_TestCase, Serial_IntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Linear2D_IEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear2D_TMD_TestCase, Serial_IntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Banana2D_IEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Banana2D_TMD_TestCase, Serial_IntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Linear1D_CBIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear1D_TMD_TestCase, Serial_CommonBasisIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_ArcTan1D_CBIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: ArcTan1D_TMD_TestCase, Serial_CommonBasisIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Exp1D_CBIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Exp1D_TMD_TestCase, Serial_CommonBasisIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Logistic1D_CBIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Logistic1D_TMD_TestCase, Serial_CommonBasisIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Gamma1D_CBIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gamma1D_TMD_TestCase, Serial_CommonBasisIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Beta1D_CBIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Beta1D_TMD_TestCase, Serial_CommonBasisIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Gumbel1D_CBIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gumbel1D_TMD_TestCase, Serial_CommonBasisIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Linear2D_CBIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear2D_TMD_TestCase, Serial_CommonBasisIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Banana2D_CBIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Banana2D_TMD_TestCase, Serial_CommonBasisIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Linear1D_TOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear1D_TMD_TestCase, Serial_TotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_ArcTan1D_TOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: ArcTan1D_TMD_TestCase, Serial_TotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Exp1D_TOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Exp1D_TMD_TestCase, Serial_TotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Logistic1D_TOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Logistic1D_TMD_TestCase, Serial_TotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Gamma1D_TOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gamma1D_TMD_TestCase, Serial_TotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Beta1D_TOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Beta1D_TMD_TestCase, Serial_TotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Gumbel1D_TOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gumbel1D_TMD_TestCase, Serial_TotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Linear2D_TOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear2D_TMD_TestCase, Serial_TotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Banana2D_TOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Banana2D_TMD_TestCase, Serial_TotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Linear1D_CBTOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear1D_TMD_TestCase, Serial_CommonBasisTotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_ArcTan1D_CBTOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: ArcTan1D_TMD_TestCase, Serial_CommonBasisTotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Exp1D_CBTOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Exp1D_TMD_TestCase, Serial_CommonBasisTotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Logistic1D_CBTOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Logistic1D_TMD_TestCase, Serial_CommonBasisTotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Gamma1D_CBTOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gamma1D_TMD_TestCase, Serial_CommonBasisTotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Beta1D_CBTOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Beta1D_TMD_TestCase, Serial_CommonBasisTotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Gumbel1D_CBTOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gumbel1D_TMD_TestCase, Serial_CommonBasisTotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Linear2D_CBTOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear2D_TMD_TestCase, Serial_CommonBasisTotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Banana2D_CBTOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Banana2D_TMD_TestCase, Serial_CommonBasisTotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Linear1D_IEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear1D_TMD_TestCase, Serial_IntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_ArcTan1D_IEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: ArcTan1D_TMD_TestCase, Serial_IntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Exp1D_IEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Exp1D_TMD_TestCase, Serial_IntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Logistic1D_IEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Logistic1D_TMD_TestCase, Serial_IntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Gamma1D_IEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gamma1D_TMD_TestCase, Serial_IntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Beta1D_IEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Beta1D_TMD_TestCase, Serial_IntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Gumbel1D_IEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gumbel1D_TMD_TestCase, Serial_IntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Linear2D_IEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear2D_TMD_TestCase, Serial_IntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Banana2D_IEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Banana2D_TMD_TestCase, Serial_IntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Linear1D_CBIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear1D_TMD_TestCase, Serial_CommonBasisIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_ArcTan1D_CBIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: ArcTan1D_TMD_TestCase, Serial_CommonBasisIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Exp1D_CBIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Exp1D_TMD_TestCase, Serial_CommonBasisIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Logistic1D_CBIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Logistic1D_TMD_TestCase, Serial_CommonBasisIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Gamma1D_CBIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gamma1D_TMD_TestCase, Serial_CommonBasisIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Beta1D_CBIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Beta1D_TMD_TestCase, Serial_CommonBasisIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Gumbel1D_CBIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gumbel1D_TMD_TestCase, Serial_CommonBasisIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Linear2D_CBIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear2D_TMD_TestCase, Serial_CommonBasisIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Banana2D_CBIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Banana2D_TMD_TestCase, Serial_CommonBasisIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Linear1D_TOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear1D_TMD_TestCase, Serial_TotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_ArcTan1D_TOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: ArcTan1D_TMD_TestCase, Serial_TotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Exp1D_TOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Exp1D_TMD_TestCase, Serial_TotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Logistic1D_TOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Logistic1D_TMD_TestCase, Serial_TotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Gamma1D_TOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gamma1D_TMD_TestCase, Serial_TotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Beta1D_TOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Beta1D_TMD_TestCase, Serial_TotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Gumbel1D_TOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gumbel1D_TMD_TestCase, Serial_TotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Linear2D_TOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear2D_TMD_TestCase, Serial_TotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Banana2D_TOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Banana2D_TMD_TestCase, Serial_TotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Linear1D_CBTOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear1D_TMD_TestCase, Serial_CommonBasisTotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_ArcTan1D_CBTOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: ArcTan1D_TMD_TestCase, Serial_CommonBasisTotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Exp1D_CBTOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Exp1D_TMD_TestCase, Serial_CommonBasisTotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Logistic1D_CBTOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Logistic1D_TMD_TestCase, Serial_CommonBasisTotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Gamma1D_CBTOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gamma1D_TMD_TestCase, Serial_CommonBasisTotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Beta1D_CBTOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Beta1D_TMD_TestCase, Serial_CommonBasisTotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Gumbel1D_CBTOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gumbel1D_TMD_TestCase, Serial_CommonBasisTotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Linear2D_CBTOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear2D_TMD_TestCase, Serial_CommonBasisTotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Banana2D_CBTOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Banana2D_TMD_TestCase, Serial_CommonBasisTotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Linear1D_ISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear1D_TMD_TestCase, Serial_IntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_ArcTan1D_ISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: ArcTan1D_TMD_TestCase, Serial_IntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Exp1D_ISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Exp1D_TMD_TestCase, Serial_IntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Logistic1D_ISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Logistic1D_TMD_TestCase, Serial_IntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Gamma1D_ISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gamma1D_TMD_TestCase, Serial_IntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Beta1D_ISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Beta1D_TMD_TestCase, Serial_IntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Gumbel1D_ISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gumbel1D_TMD_TestCase, Serial_IntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Linear2D_ISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear2D_TMD_TestCase, Serial_IntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Banana2D_ISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Banana2D_TMD_TestCase, Serial_IntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Linear1D_TOISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear1D_TMD_TestCase, Serial_TotOrdIntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_ArcTan1D_TOISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: ArcTan1D_TMD_TestCase, Serial_TotOrdIntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Exp1D_TOISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Exp1D_TMD_TestCase, Serial_TotOrdIntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Logistic1D_TOISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Logistic1D_TMD_TestCase, Serial_TotOrdIntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Gamma1D_TOISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gamma1D_TMD_TestCase, Serial_TotOrdIntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Beta1D_TOISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Beta1D_TMD_TestCase, Serial_TotOrdIntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Gumbel1D_TOISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gumbel1D_TMD_TestCase, Serial_TotOrdIntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Linear2D_TOISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear2D_TMD_TestCase, Serial_TotOrdIntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Banana2D_TOISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Banana2D_TMD_TestCase, Serial_TotOrdIntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Linear1D_ISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear1D_TMD_TestCase, Serial_IntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_ArcTan1D_ISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: ArcTan1D_TMD_TestCase, Serial_IntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Exp1D_ISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Exp1D_TMD_TestCase, Serial_IntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Logistic1D_ISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Logistic1D_TMD_TestCase, Serial_IntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Gamma1D_ISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gamma1D_TMD_TestCase, Serial_IntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Beta1D_ISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Beta1D_TMD_TestCase, Serial_IntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Gumbel1D_ISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gumbel1D_TMD_TestCase, Serial_IntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Linear2D_ISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear2D_TMD_TestCase, Serial_IntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Banana2D_ISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Banana2D_TMD_TestCase, Serial_IntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Linear1D_TOISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear1D_TMD_TestCase, Serial_TotOrdIntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_ArcTan1D_TOISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: ArcTan1D_TMD_TestCase, Serial_TotOrdIntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Exp1D_TOISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Exp1D_TMD_TestCase, Serial_TotOrdIntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Logistic1D_TOISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Logistic1D_TMD_TestCase, Serial_TotOrdIntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Gamma1D_TOISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gamma1D_TMD_TestCase, Serial_TotOrdIntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Beta1D_TOISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Beta1D_TMD_TestCase, Serial_TotOrdIntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Gumbel1D_TOISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gumbel1D_TMD_TestCase, Serial_TotOrdIntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Linear2D_TOISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear2D_TMD_TestCase, Serial_TotOrdIntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Banana2D_TOISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Banana2D_TMD_TestCase, Serial_TotOrdIntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Linear1D_LSPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear1D_TMD_TestCase, Serial_LinearSpanPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Serial_Linear1D_CBLSPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear1D_TMD_TestCase, Serial_CommonBasisLinearSpanPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Linear1D_IEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear1D_TMD_TestCase, Parallel_IntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_ArcTan1D_IEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: ArcTan1D_TMD_TestCase, Parallel_IntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Exp1D_IEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Exp1D_TMD_TestCase, Parallel_IntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Logistic1D_IEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Logistic1D_TMD_TestCase, Parallel_IntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Gamma1D_IEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gamma1D_TMD_TestCase, Parallel_IntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Beta1D_IEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Beta1D_TMD_TestCase, Parallel_IntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Gumbel1D_IEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gumbel1D_TMD_TestCase, Parallel_IntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Linear2D_IEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear2D_TMD_TestCase, Parallel_IntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Banana2D_IEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Banana2D_TMD_TestCase, Parallel_IntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Linear1D_CBIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear1D_TMD_TestCase, Parallel_CommonBasisIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_ArcTan1D_CBIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: ArcTan1D_TMD_TestCase, Parallel_CommonBasisIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Exp1D_CBIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Exp1D_TMD_TestCase, Parallel_CommonBasisIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Logistic1D_CBIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Logistic1D_TMD_TestCase, Parallel_CommonBasisIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Gamma1D_CBIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gamma1D_TMD_TestCase, Parallel_CommonBasisIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Beta1D_CBIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Beta1D_TMD_TestCase, Parallel_CommonBasisIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Gumbel1D_CBIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gumbel1D_TMD_TestCase, Parallel_CommonBasisIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Linear2D_CBIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear2D_TMD_TestCase, Parallel_CommonBasisIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Banana2D_CBIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Banana2D_TMD_TestCase, Parallel_CommonBasisIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Linear1D_TOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear1D_TMD_TestCase, Parallel_TotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_ArcTan1D_TOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: ArcTan1D_TMD_TestCase, Parallel_TotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Exp1D_TOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Exp1D_TMD_TestCase, Parallel_TotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Logistic1D_TOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Logistic1D_TMD_TestCase, Parallel_TotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Gamma1D_TOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gamma1D_TMD_TestCase, Parallel_TotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Beta1D_TOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Beta1D_TMD_TestCase, Parallel_TotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Gumbel1D_TOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gumbel1D_TMD_TestCase, Parallel_TotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Linear2D_TOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear2D_TMD_TestCase, Parallel_TotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Banana2D_TOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Banana2D_TMD_TestCase, Parallel_TotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Linear1D_CBTOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear1D_TMD_TestCase, Parallel_CommonBasisTotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_ArcTan1D_CBTOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: ArcTan1D_TMD_TestCase, Parallel_CommonBasisTotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Exp1D_CBTOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Exp1D_TMD_TestCase, Parallel_CommonBasisTotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Logistic1D_CBTOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Logistic1D_TMD_TestCase, Parallel_CommonBasisTotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Gamma1D_CBTOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gamma1D_TMD_TestCase, Parallel_CommonBasisTotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Beta1D_CBTOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Beta1D_TMD_TestCase, Parallel_CommonBasisTotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Gumbel1D_CBTOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gumbel1D_TMD_TestCase, Parallel_CommonBasisTotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Linear2D_CBTOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear2D_TMD_TestCase, Parallel_CommonBasisTotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Banana2D_CBTOIEPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Banana2D_TMD_TestCase, Parallel_CommonBasisTotOrdIntegratedExponentialPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Linear1D_IEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear1D_TMD_TestCase, Parallel_IntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_ArcTan1D_IEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: ArcTan1D_TMD_TestCase, Parallel_IntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Exp1D_IEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Exp1D_TMD_TestCase, Parallel_IntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Logistic1D_IEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Logistic1D_TMD_TestCase, Parallel_IntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Gamma1D_IEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gamma1D_TMD_TestCase, Parallel_IntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Beta1D_IEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Beta1D_TMD_TestCase, Parallel_IntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Gumbel1D_IEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gumbel1D_TMD_TestCase, Parallel_IntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Linear2D_IEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear2D_TMD_TestCase, Parallel_IntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Banana2D_IEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Banana2D_TMD_TestCase, Parallel_IntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Linear1D_CBIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear1D_TMD_TestCase, Parallel_CommonBasisIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_ArcTan1D_CBIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: ArcTan1D_TMD_TestCase, Parallel_CommonBasisIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Exp1D_CBIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Exp1D_TMD_TestCase, Parallel_CommonBasisIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Logistic1D_CBIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Logistic1D_TMD_TestCase, Parallel_CommonBasisIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Gamma1D_CBIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gamma1D_TMD_TestCase, Parallel_CommonBasisIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Beta1D_CBIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Beta1D_TMD_TestCase, Parallel_CommonBasisIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Gumbel1D_CBIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gumbel1D_TMD_TestCase, Parallel_CommonBasisIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Linear2D_CBIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear2D_TMD_TestCase, Parallel_CommonBasisIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Banana2D_CBIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Banana2D_TMD_TestCase, Parallel_CommonBasisIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Linear1D_TOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear1D_TMD_TestCase, Parallel_TotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_ArcTan1D_TOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: ArcTan1D_TMD_TestCase, Parallel_TotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Exp1D_TOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Exp1D_TMD_TestCase, Parallel_TotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Logistic1D_TOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Logistic1D_TMD_TestCase, Parallel_TotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Gamma1D_TOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gamma1D_TMD_TestCase, Parallel_TotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Beta1D_TOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Beta1D_TMD_TestCase, Parallel_TotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Gumbel1D_TOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gumbel1D_TMD_TestCase, Parallel_TotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Linear2D_TOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear2D_TMD_TestCase, Parallel_TotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Banana2D_TOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Banana2D_TMD_TestCase, Parallel_TotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Linear1D_CBTOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear1D_TMD_TestCase, Parallel_CommonBasisTotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_ArcTan1D_CBTOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: ArcTan1D_TMD_TestCase, Parallel_CommonBasisTotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Exp1D_CBTOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Exp1D_TMD_TestCase, Parallel_CommonBasisTotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Logistic1D_CBTOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Logistic1D_TMD_TestCase, Parallel_CommonBasisTotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Gamma1D_CBTOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gamma1D_TMD_TestCase, Parallel_CommonBasisTotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Beta1D_CBTOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Beta1D_TMD_TestCase, Parallel_CommonBasisTotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Gumbel1D_CBTOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gumbel1D_TMD_TestCase, Parallel_CommonBasisTotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Linear2D_CBTOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear2D_TMD_TestCase, Parallel_CommonBasisTotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Banana2D_CBTOIEPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Banana2D_TMD_TestCase, Parallel_CommonBasisTotOrdIntegratedExponentialPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Linear1D_ISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear1D_TMD_TestCase, Parallel_IntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_ArcTan1D_ISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: ArcTan1D_TMD_TestCase, Parallel_IntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Exp1D_ISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Exp1D_TMD_TestCase, Parallel_IntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Logistic1D_ISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Logistic1D_TMD_TestCase, Parallel_IntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Gamma1D_ISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gamma1D_TMD_TestCase, Parallel_IntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Beta1D_ISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Beta1D_TMD_TestCase, Parallel_IntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Gumbel1D_ISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gumbel1D_TMD_TestCase, Parallel_IntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Linear2D_ISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear2D_TMD_TestCase, Parallel_IntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Banana2D_ISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Banana2D_TMD_TestCase, Parallel_IntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Linear1D_TOISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear1D_TMD_TestCase, Parallel_TotOrdIntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_ArcTan1D_TOISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: ArcTan1D_TMD_TestCase, Parallel_TotOrdIntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Exp1D_TOISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Exp1D_TMD_TestCase, Parallel_TotOrdIntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Logistic1D_TOISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Logistic1D_TMD_TestCase, Parallel_TotOrdIntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Gamma1D_TOISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gamma1D_TMD_TestCase, Parallel_TotOrdIntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Beta1D_TOISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Beta1D_TMD_TestCase, Parallel_TotOrdIntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Gumbel1D_TOISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gumbel1D_TMD_TestCase, Parallel_TotOrdIntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Linear2D_TOISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear2D_TMD_TestCase, Parallel_TotOrdIntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Banana2D_TOISPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Banana2D_TMD_TestCase, Parallel_TotOrdIntegratedSquaredPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Linear1D_ISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear1D_TMD_TestCase, Parallel_IntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_ArcTan1D_ISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: ArcTan1D_TMD_TestCase, Parallel_IntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Exp1D_ISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Exp1D_TMD_TestCase, Parallel_IntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Logistic1D_ISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Logistic1D_TMD_TestCase, Parallel_IntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Gamma1D_ISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gamma1D_TMD_TestCase, Parallel_IntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Beta1D_ISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Beta1D_TMD_TestCase, Parallel_IntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Gumbel1D_ISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gumbel1D_TMD_TestCase, Parallel_IntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Linear2D_ISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear2D_TMD_TestCase, Parallel_IntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Banana2D_ISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Banana2D_TMD_TestCase, Parallel_IntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Linear1D_TOISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear1D_TMD_TestCase, Parallel_TotOrdIntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_ArcTan1D_TOISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: ArcTan1D_TMD_TestCase, Parallel_TotOrdIntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Exp1D_TOISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Exp1D_TMD_TestCase, Parallel_TotOrdIntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Logistic1D_TOISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Logistic1D_TMD_TestCase, Parallel_TotOrdIntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Gamma1D_TOISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gamma1D_TMD_TestCase, Parallel_TotOrdIntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Beta1D_TOISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Beta1D_TMD_TestCase, Parallel_TotOrdIntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Gumbel1D_TOISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Gumbel1D_TMD_TestCase, Parallel_TotOrdIntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Linear2D_TOISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear2D_TMD_TestCase, Parallel_TotOrdIntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Banana2D_TOISPFTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Banana2D_TMD_TestCase, Parallel_TotOrdIntegratedSquaredPFTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Linear1D_LSPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear1D_TMD_TestCase, Parallel_LinearSpanPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

class TransportMaps.tests.test_transportmap_distributions_sampling.Parallel_Linear1D_CBLSPBTMD_SamplingCheck(methodName='runTest')[source]¶

Bases: Linear1D_TMD_TestCase, Parallel_CommonBasisLinearSpanPBTMD_SamplingCheck, 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

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()[source]¶: Hook method for setting up the test fixture before exercising it.

TransportMaps.tests.test_transportmap_distributions_sampling.build_suite(ttype='all')[source]¶

TransportMaps.tests.test_transportmap_distributions_sampling.run_tests(ttype='serial', failfast=False)[source]¶

TransportMaps.tests.test_transportmap_distributions_sampling¶

Module Contents¶

Classes¶

Functions¶

`TransportMaps.tests.test_transportmap_distributions_sampling`¶