Skip to content

Instantly share code, notes, and snippets.

View blazetopher's full-sized avatar

Christopher Mueller blazetopher

View GitHub Profile

Hi all,

Luke and I just discussed the workflow for calculating Derived Parameters that require input from multiple Data Products – as is the case for calculating the L2 DOCONCS from DOSTA and CTD inputs (see section 2.2.2 of [DOCONCS DataProduct spec] [2]).

While the combinatorial functionality required at the Coverage Model level is already in place, there are some gaps in the resource, association, and preload layers of the system required to orchestrate this type of DataProduct. Here are the gaps that would need to be filled to realize an AggregateDataProduct (working name):

  • Resource stuff:
    • New resource – AggregateDataProduct: extends DataProduct
    • Adds fields:
  • complex_coverage_type or
@blazetopher
blazetopher / README.md
Last active December 18, 2015 02:08
Examples of test function reuse through multiple inheritance and the get_props decorator for test-specific properties

##Test Reuse via Multiple Inheritance This pattern allows reuse of the same set of "core" tests across many concrete implementations of a class hierarchy. The tests can be written to test core functionality while concrete test classes provide specifics geared towards each concrete implementation. In conjunction with the get_props decorator, this pattern can provide a very high degree of test reuse (resulting in increased test coverage) without sacrificing the specificity for concrete implementations. Addition of new concrete tests gets the benefit of all of the base tests with only a relatively small amount of property configuration.

##get_props Decorator Evaluates the contents of TESTING_PROPERTIES on a test-by-test basis and Provides a self.method_name.props attribute to the method that contains a dictionary of properties

The TESTING_PROPERTIES dictionary can be extended/amended by subclasses to provide specific properties on a class-wide and/or test-by-test basis

@blazetopher
blazetopher / hash.py
Last active December 19, 2015 05:09
Function to recursively hash an item of any (nearly) type, including full objects.
from collections import Hashable
try:
import numpy as np
has_np=True
except ImportError:
has_np=False
def hash_any(value, hv=None):
hv = hv or 0
@blazetopher
blazetopher / gomarkgo.md
Last active August 29, 2015 14:19
Get Mark Going

Setup

If you don't have a ~/Development directory, make one:

cd ~
mkdir Development

Go into the Development directory:

cd ~/Development
@blazetopher
blazetopher / SHARC-Meeting-Notes.md
Created April 21, 2015 16:45
Notes from SHARC Dev Meetings

4/21/2015

Modeling stuff

  • Brief review of Chris’ changes over the last month
  • Brief review of Pete’s work on Radioactive Decay and Volatilization
    • AI - Chris to incorporate Radioactive Decay into AqFates
    • Implementing temperature correction for case –1 Henry’s Law Constants
      • AI - Pete to add logic to do temperature correction for HLC across the board
    • Sorting out particle radius determination for Volatilization
      • AI - Pete and Jenna to spend ~1hr investigating new equation for volatilization. If unavailable/impractical, will use existing equation, but will spend another ~1hr fixing it.
  • Sorting out the density adjustment when incorporating a constituent into a composite