Data

Tools

Indexes

Applications

Experiments

Open Source Science

smoke

Gordon Group space

https://github.com/c3aidti/smoke

Science Score: 54.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • ✓
    CITATION.cff file
    Found CITATION.cff file
  • ✓
    codemeta.json file
    Found codemeta.json file
  • ✓
    .zenodo.json file
    Found .zenodo.json file
  • ○
    DOI references
  • ✓
    Academic publication links
    Links to: zenodo.org
  • ○
    Academic email domains
  • ○
    Institutional organization owner
  • ○
    JOSS paper metadata
  • ○
    Scientific vocabulary similarity
    Low similarity (11.0%) to scientific vocabulary
Last synced: 6 months ago · JSON representation ·

Repository

Gordon Group space

Basic Info
  • Host: GitHub
  • Owner: c3aidti
  • License: mit
  • Language: Jupyter Notebook
  • Default Branch: main
  • Size: 15.4 MB
Statistics
  • Stars: 0
  • Watchers: 4
  • Forks: 0
  • Open Issues: 10
  • Releases: 1
Created almost 4 years ago · Last pushed about 1 year ago
Metadata Files
Readme License Citation

README.md

DOI

smoke

Hamish Gordon's group space for development and deployment of C3 AI DTI applications.

Main components

The smoke space in C3's IDS, which lives in DTI RC01, currently has one application (smokeApp) and one branch (dev/smokeApp/rc1). The latter corresponds to a C3 tag that can be access via the vanity URL https://devsmokeapprc1-smokeapp.devrc01.c3aids.cloud/static/console/

Typical development workflow

This GitHub repository always contains at least three branches:

  • an intrinsic main branch that hosts the application code for each released version.
  • a C3 develop branch that is connected to C3 AI Studio (formerly IDS)
  • dev branches that represents what is deployed to the tag above

The typical development workflow then goes as follows:

  1. Clone the repository to your local environment (we highly encourage using VS Code)
  2. Create a new branch from dev/smokeApp/rc1 and give it a meaningful name, e.g. username-dev
  3. Develop code, regularly commit, and push back to GitHub when you want the code provisioned to the tag
  4. Open a pull request from username-dev into dev/smokeApp/rc1
  5. Github Actions that DTI DevOps have running will then trigger the provisioning of the package to the dev/smokeApp/rc1 tag (URL above)

As long as the pull request is open, pushing code to GitHub will always trigger the provisioning workflow. For that reason, if you have multiple developers in your team, we recommend that you consider more ephemeral pull requests to tackle simple tasks at a time. You are welcome to use GitHub Projects to give them tags and other details, as well as using GitHub Issues to describe the steps of more complex development efforts that can then be broken into several small tasks, each one with its own PR (open, close, next).

Owner

  • Name: C3.ai DTI
  • Login: c3aidti
  • Kind: organization

C3.ai Digital Transformation Institute

Citation (CITATION.cff) 

cff-version: 1.0.0
message: "If you use this software, please cite it as below."
authors:
- family-names: "Abreu"
  given-names: "Bruno"
  orcid: "https://orcid.org/0000-0002-9067-779X"
  affiliation: "University of Illinois at Urbana-Champaign"
- family-names: "Adams"
  given-names: "Darren"
  affiliation: "University of Illinois at Urbana-Champaign"
- family-names: "Carzon"
  given-names: "James"
  orcid: "https://orcid.org/0009-0000-1038-5475"
  affiliation: "Carnegie Mellon University"
- family-names: "Gordon"
  given-names: "Hamish"
  affiliation: "Carnegie Mellon University"
title: "c3aidti/smoke: Scalable ML framework for UKESM1 climate model data"
version: v1.0.0
date-released: 2023-03-31
doi: 10.5281/zenodo.7789889
repository-code: "https://github.com/c3aidti/smoke"

GitHub Events

Total
  • Push event: 3
Last Year
  • Push event: 3

Dependencies

smoke/smokeApp/package.json npm
  • standardDependencies