ITK VS starter-workflows

The itkImage.h header is ITK's standard n-dimensional image data structure.

In this post, we review how the Insight Toolkit (ITK) leverages the first-interaction GitHub Action to communicate our appreciation of the efforts of first-time contributors, establish norms for behavior, and provide civil pointers on where to find more information.

Jupyter has emerged as a fundamental component in artificial intelligence (AI) solution development and scientific inquiry. Jupyter notebooks are prevelant in modern education, commercial applications, and academic research. The Insight Toolkit (ITK) is an open source, cross-platform toolkit for N-dimensional processing, segmentation, and registration used to obtain quantitative insights from medical, biomicroscopy, material science, and geoscience images. The ITK community highly values scientific reproducibility and software sustainability. As a result, advanced computational methods in the toolkit have a dramatically larger impact because they can be reproducibly applied in derived research or commercial applications.

It also depends heavily on the toolchain. One of the first successful toolkits used to circumvent image-based security measures was ITK, originally a toolkit for medical image processing. That's not even using AI (at least back then). Here you build "piplines" by lego'ing together functions like building blocks, there are rules to it, but the sleek interface design make it very versatile. It was a nightmare to devise ways to counteract, since the crucial processing steps could easily be switched around as long as the linear algebra made sense. And when you have a toolchain excelling in fourier-space based analysis and interaction, the linear algebra makes sense in a lot of different orders of doing steps.

Yeah, Prolog is pretty cool!

Another technology I found interesting too learn is ITK (https://itk.org/). You need a different mindset using ITK than other image processing libraries.

Lisp is cool as well.

And fully homomorphic encryption.

VTK is a powerful visualization package, but it's more for working with 3D FEM/CFD data. There are lots of things in there though, so it may be useful. The sister project Paraview is an application which can be used to work with data interactively. Both have great Python support. There is also ITK which is focused on with image data, like medical scans - never used it, though.

GitHub Actions is GitHub's CI/CD solution. You can use it to run automated tasks each time you change your code. Although the platform lacks a built-in Kubernetes integration, third-party plugins such as Azure's Deploy to Kubernetes Cluster action can automate deployments and manage different rollout strategies.

GitHub Actions is a feature-rich CI/CD platform embedded within GitHub, enabling developers to automate, customize, and execute software development workflows directly in their repositories. An Action inside GitHub Actions is a discrete unit of automation that performs a specific task within a workflow. All the Actions are reusable, and there are many to choose from. You can even create your own reusable ones.

actions/starter-workflows

The real power of using PHP code-quality tools is when it’s added to your continuous integration process, which means it automatically checks the code every time someone makes a push or pull request to your project repo. In this section, we'll be looking at how to do just that. GitHub actions is available for free so we'll use it for demo purposes. Note that there are some limits to private repos, so set your test repo to public if you can.

You can even automate the running of this script — hence the directory name automation — to happen every time the data changes, using GitHub Actions.

# Based on https://github.com/actions/starter-workflows/blob/main/ci/node.js.yml name: CI on: pull_request: branches: - main jobs: ci: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - uses: actions/setup-node@v2 with: node-version: lts/* cache: 'npm' - run: npm ci - run: npm run build --if-present - run: npm test

You might remember that I’ve been taking an interest in GitHub Actions for the last year or so (I even wrote a book on the subject). And at the Perl Conference in Toronto last summer I gave a talk called “GitHub Actions for Perl Development” (here are the slides and the video).

Preevy is designed to be easily run in CI/CD workflows, such as GH Actions, Circle CI and others.

I set out to add further development and contribution tools to my ez-txt2html converter. Specifically, I wanted to introduce an initial Continuous Integration workflow. For this, I used the “Python Application” workflow template in Github Actions to create a CI testing workflow that builds a Py v3.12 environments, builds the project dependencies, runs Flake8 linting and Black formatting and then subsequently runs PyTest using the test suites I’ve written previously.

GitHub Actions