Skip to content

Home

Jump to bottom
JEJodesty edited this page Jul 26, 2024 · 98 revisions

Weekly Log

January:

Week 0 (1/2 - 1/5):

Update readme and refactor

Week 1 (1/8 - 1/12):

Week 2 (1/15 - 1/19):

  • Research Dynamic Terraform Providers for Plant Deployments
  • Verify CATs’ Project Update: Structure Block Design, Data Service Collaboration Diagram, Ray Integration
  • Watched Computational Governance Panel
  • Review Ray documentation for InfraFunction Hooks
  • Research Open Contracting Data Standard with respect to Data Product Teams: https://standard.open-contracting.org/latest/en/

Week 3 (1/22 - 1/26)

  • 1/22:
    • Updated CATs integration tests and demo
    • Resolved dependency bug
    • Verify CATs’ Project Update: Process Component, Sub-Process Logging, Executor & Function Components
  • 1/23:
    • Updated Documentation and Demo
    • Added License and Packaging for CATs
    • Verify CATs’ Project Update: s3 & CoD Integration
  • 1/24:
    • Updated Documentation & Refactor
    • CATs Data Verification
    • Verify CATs’ Project Update: Updating Order Structure, Node, Service & Structure Components
  • 1/25 - 1/26:
    • Updated Documentation & Refactor
    • Update Factory
    • Reviewed Novo Nordisk Data Mesh Platform discussion
    • Verify CATs’ Project Update: CATs s3 cache, BOM ERD

February:

Week 4 (1/29 - 2/2):

  • Included Ubuntu 20.04 Installation Update
  • Refactored CATs
  • Researched CAT cache access management
  • Research Economic Adapters for CATs from Ocean Protocol
  • Research multilevel linked-list for CATs’ subgraph

Week 5 (2/5 – 2/9):

Week 6 (2/12 - 2/16):

  • 2/12: Drafted CATs capabilities in GitHub Project and reviewed Activity Artifact Policy
  • 2/13: Reviewed implementation examples of Data Contracts
  • 2/14 - 2/15:
    • Reviewed Data Mesh Roundtable Discussions about Data Contracts and “Agile” Data Products
    • Attended Protocol Labs project updates
  • 2/16:
    • Research System Architecture layers and wrote notes as Data Contract Article for CATs
  • Wrote Article: What does a CATs data contract do?

Data Mesh Resources:

Data Contract Implementation Examples:

System Architecture:

Week 7 (2/19 - 2/23):

  • 2/19 - 2/21: Contextualize value of BOM within the context of Data as a Product that contains Data Contracts
  • 2/22 - 2/23: Updated Readme informed by examples of Data Assets within the context of Machine-Readable Cataloging
  • Wrote Article: What is a Content-Addressed Data Asset (CADA)?

Resources:

March:

Week 8 (2/26 - 3/1):

Week 9 (3/4 - 3/8):

Resources:

Week 10 (3/11 - 3/15):

Week 11 (3/18 - 3/22):

Week 12 (3/25 - 3/29):

April:

Week 13 (4/1 - 4/5):

Week 14 (4/8 - 4/12):

Week 15 (4/15 - 4/19):

Week 16 (4/22 - 4/26):

May:

Week 17 (4/29 - 5/3):

Week 18 (5/6 - 5/10):

  • Removing s3 cache from CATs and replace with local storage solution

Week 19 (5/13 - 5/17):

Week 20 (5/19 - 5/24):

  • The Plant is a Transfer Function that accepts an Order as Input and produces and Output with by executing Function (Process) with Executor (Actuator) that executes a Process(es). The Plant exposes the control variable (u(t)) for Control Feedback Loop and the Function (Process) produces the process variable (y(t)). The Process Variable is the Statistical Process Control of CATs Dataset I/O (Ingress/Egress)
  • Docker can be executed within an Alpine Linux Docker container ["Docker in Docker" (DinD)] for upcoming cadCAD's nested Block executions as a summation of the control variable (u(t)) that configure CATs Data Product and the summation of the process variable (y(t))
  • Note: "Integral windup particularly occurs as a limitation of physical systems, compared with ideal systems, due to the ideal output being physically impossible (process saturation: the output of the process being limited at the top or bottom of its scale, making the error constant)."
  • Concern: "Integral windup particularly occurs as a limitation of physical systems, compared with ideal systems, due to the ideal output being physically impossible (process saturation: the output of the process being limited at the top or bottom of its scale, making the error constant)."
    • https://en.wikipedia.org/wiki/Integral_windup
    • Alleviated by "A CAT at its core is a unit of computational work specified by the triplet 1) what the input is, 2) what does the computation, and 3) what the output is. Controllers require feedback, which is currently outside of the scope of a single cat. Any cyclic orchestration must be external to CATs." - BlockScience
  • Alpine Linux Docker can be the execution paradigm of cadCAD and CATs Plant because they can run as Docker inside Docker "DinD” to and functionally map cadCAD multi-dimensional blocks to CAT Functions

Week 21 (5/27 - 5/31):

June:

Week 22 (6/3 - 6/7):

  • Updated Bacalhau Node and refactor for CoD interoperability for CATs v3
  • Exposed ingress and egress to action plane via Process with a interoperable integration point for CATs v3

Week 23 (6/10 - 6/14):

  • Included data product disciplines to CATs Architectural Quantum for CATs v3
  • Implement InfraStructure Sub Component separately

Week 24 (6/17 - 6/26):

  • IPFS daemon initiated by CAT Node
  • partially implement function for applying sbom
  • Refactor infrafunction composes Processor & Plant and Infrstructure
  • Installed KMS locally for cat/rid Integration

Week 24 (6/24 - 6/28):

July:

Week 25 (7/1 - 7/5):

Week 26 (7/8 - 7/12):

Clone this wiki locally