2017-03-31 02:38:29 +05:30
2017-07-08 19:03:38 +05:30
2017-07-24 16:25:45 +02:00
2017-01-01 16:10:50 -05:00
2017-06-30 07:57:17 -04:00
2017-07-07 01:19:31 +05:30
2017-07-04 21:39:14 +05:30
2017-01-02 20:09:33 -05:00
2017-07-24 16:25:45 +02:00
2017-07-10 18:53:37 +05:30

Image Sequencer

aka "Consequencer"

Build Status

Why

Image Sequencer is different from other image processing systems in that it's non-destructive: instead of modifying the original image, it creates a new image at each step in a sequence. This is because it:

  • produces a legible trail of operations, to "show your work" for evidential, educational, or reproducibility reasons
  • makes the creation of new tools or "modules" simpler -- each must accept an input image, and produce an output image
  • allows many images to be run through the same sequence of steps

It is also for prototyping some other related ideas:

  • filter-like image processing -- applying a transform to any image from a given source, like a proxy. I.e. every image tile of a satellite imagery web map
  • test-based image processing -- the ability to create a sequence of steps that do the same task as some other image processing tool, provable with example before/after images to compare with
  • logging of each step to produce an evidentiary record of modifications to an original image
  • cascading changes -- change an earlier step's settings, and see those changes affect later steps
  • "small modules"-based extensibility: see Contributing, below

Examples:

Quick Usage

Image Sequencer can be used to run modules on an HTML Image Element using the replaceImage method. The method accepts two parameters - selector and steps. selector is a CSS selector. If it matches multiple images, all images will be modified. steps may be the name of a module or array of names of modules.

Note: Browser CORS Restrictions apply. Some browsers may not allow local images form other folders, and throw a Security Error instead.

  sequencer.replaceImage(selector,steps,optional_options);

optional_options allows to pass additional arguments to the module itself.

For example:

  sequencer.replaceImage('#photo','invert');
  sequencer.replaceImage('#photo',['invert','ndvi-red']);

Classic Usage

Initializing the Sequencer

The Image Sequencer Library exports a function ImageSequencer which initializes a sequencer.

var sequencer = ImageSequencer();

Loading an Image into the Sequencer

The loadImage method is used to load an image into the sequencer. It accepts a name and an image. The method also accepts an optional callback.

sequencer.loadImage(image_src,optional_callback);

On Node.js the image_src may be a DataURI or a local path. On browsers, it must be a DatURI (or 'selector to image' -- Work in Progress)

return value: sequencer (To allow method chaining)

Adding steps to the image

The addSteps method is used to add steps on the image. One or more steps can be added at a time. Each step is called a module.

sequencer.addSteps(modules, optional_options);

If only one module is to be added, modules is simply the name of the module. If multiple images are to be added, modules is an array of the names of modules which are to be added, in that particular order.

optional_otions is just additional parameters, in object form, which you might want to provide to the modules. It's an optional parameter.

return value: sequencer (To allow method chaining)

Running the Sequencer

Once all steps are added, This method is used to generate the output of all these modules.

sequencer.run();

Additionally, an optional callback can be passed to this method.

sequencer.run(function(out){
  // this gets called back.
  // "out" is the DataURL of the final image.
});

return value: sequencer (To allow method chaining)

Removing a step from the sequencer

The removeSteps method is used to remove unwanted steps from the sequencer. It accepts the index of the step as an input, or an array of the unwanted indices if there are more than one.

For example, if the modules ['ndvi-red','crop','invert'] were added in this order, and I wanted to remove 'crop' and 'invert', I can either do this:

sequencer.removeSteps(2);
sequencer.removeSteps(3);

or:

sequencer.removeSteps([2,3]);

return value: sequencer (To allow method chaining)

Inserting a step in between the sequencer

The insertSteps method can be used to insert one or more steps at a given index in the sequencer. It accepts the index where the module is to be inserted, name of the module, and an optional options parameter. index is the index of the inserted step. Only one step can be inserted at a time. optional_options plays the same role it played in addSteps.

Indexes can be negative. Negative sign with an index means that counting will be done in reverse order. If the index is out of bounds, the counting will wrap in the original direction of counting. So, an index of -1 means that the module is inserted at the end.

sequencer.insertSteps(index,module_name,optional_options);

return value: sequencer (To allow method chaining)

Method Chaining

Methods can be chained on the Image Sequencer:

  • run() can not be in the middle of the chain.
  • If the chain starts with loadImage() or loadImages(), the following methods are applied only to the newly loaded images.
  • If no name is provided to the image, a name will be generated for it. The name will be of the form "image". For ex: "image1", "image2", "image3", etc.

Valid Chains:

sequencer.loadImage('red').addSteps('invert').run(function(out){
  //do something with otuput.
});
sequencer.addSteps(['ndvi-red','invert']).run();
et cetra.

Invalid Chains:

sequencer.addSteps('invert').run().addSteps('ndvi-red');

Multiple Images

Image Sequencer is capable of handling multiple images at once.

Initializing a sequencer with multiple images.

This is just like before.

var sequencer = ImageSequencer();

Loading Multiple Images into the Sequencer

Multiple images can be loaded by the method loadImages. Everything is the same, except that now, a unique identification called image_name has to be provided with each image. This is a string literal.

  • 3/2 parameters :
    sequencer.loadImages(image_name,
      image_src,optional_callback);
    
  • 1/2 parameters (JSON) :
    sequencer.loadImages({
      images: {
        image1_name: image_src,
        image2_name: image_src,
        ...
      },
      callback: optional_callback
    });
    

return value: sequencer (To allow method chaining)

Adding Steps on Multiple Images

The same method addSteps is used for this. There's just a slight obvious change in the syntax that the image name has to be supplied too. image_name as well as module_name in the following examples can be either strings or arrays of strings.

sequencer.addSteps(image_name,module_name,optional_options);

If no Image Name is specified, the module is added to all images.

sequencer.addSteps(module_name,optional_options);

All this can be passed in as JSON:

sequencer.addSteps({
  image1_name: {name: module_name, o: optional_options},
  image2_name: {name: module_name, o: optional_options},
  ...
});

return value: sequencer (To allow method chaining)

Running a Sequencer with multiple images

The same run method can be used with a slight change in syntax. The run method accepts parameters image and from. from is the index from where the function starts generating output. By default, it will run across all the steps. (from = 1) If no image is specified, the sequencer will be run over all the images. image_name may be an array of image names.

sequencer.run(); //All images from first step
sequencer.run(image_name,from); //Image 'image' from 'from'

The run method also accepts an optional callback just like before:

  sequencer.run(image_name,from,function(out){
    // This gets called back.
    // "out" is the DataURL of final image.
  });

JSON Input is also acceptable.

sequencer.run({
  image1_name: from,
  image2_name: from,
  ...
});

return value: sequencer (To allow method chaining)

Removing Steps from an Image

Similarly, removeSteps can also accept an image_name parameter. Either, both, or none of image_name and steps them may be an array. JSON input is also acceptable.

sequencer.removeSteps("image_name",[steps]);
sequencer.removeSteps("image_name",step);
sequencer.removeSteps({
  image1_name: [steps],
  image2_name: [steps],
  ...
});

return value: sequencer (To allow method chaining)

Inserting steps on an image

The insertSteps method can also accept an image_name parameter. image_name may be an array. Everything else remains the same. JSON Inout is acceptable too.

sequencer.insertSteps("image",index,"module_name",o);
sequencer.insertSteps([image],index,"module_name",o);
sequencer.insertSteps({
  image1: [
    {index:index1, name: module_name1, o:optional_options1},
    {index:index2, name: module_name2, o:optional_options2},
    ...
  ]
});

return value: sequencer (To allow method chaining)

Contributing

Happily accepting pull requests; to edit the core library, modify files in /src/. To build, run npm install and grunt build.

Contributing modules

Most contribution (we imagine) would be in the form of API-compatible modules, which need not be directly included.

draw()

To add a module to Image Sequencer, it must have the following method; you can wrap an existing module to add them:

  • module.draw()

The draw(input,callback) method should accept an input parameter, which will be an object of the form:

input = {
  src: "datauri here",
  format: "jpeg/png/etc"
}

The image object is essentially the output of the previous step.

The draw method must, when it is complete, pass the output image to the method this.output = modified_input, which will send the output to the next module in the chain. For example:

function draw(image) {

  // do some stuff with the image

  this.output = image;
  callback();
}

Title

For display in the web-based UI, each module may also have a title like options.title.

Module example

See existing module green-channel for an example: https://github.com/jywarren/image-sequencer/tree/master/src/modules/GreenChannel.js

For help integrating, please open an issue.


Development

Notes on development next steps:

UI

  • add createUserInterface() which is set up by default to draw on ImageBoardUI, but could be swapped for nothing, or an equiv. lib

  • it could create the interface and use event listeners like module.on('draw', fn()); to update the interface

  • spinners before panels are complete

  • is there a module for generating forms from parameters?

  • click to expand for all images

  • ImageSequencer.Renderer class to manage image output formats and adapters

  • remove step

  • output besides an image -- like message(txt) to display to the step's UI

Modularization

  • remotely includable modules, not compiled in -- see plugin structures in other libs
  • ability to start running at any point -- already works?
  • commandline runnability?
    • Make available as browserified OR require() includable...
  • standardize panel addition with submodule that offers Panel.display(image)
  • allow passing data as data-uri or Image object, or stream, or ndarray or ImageData array, if both of neighboring pair has ability?
  • ...could we directly include package.json for module descriptions? At least as a fallback.
  • (for node-and-line style UIs) non-linear sequences with Y-splitters
  • sequencer.addModule('path/to/module.js') style module addition -- also to avoid browserifying all of Plotly :-P
  • remove step

Testing

  • tests - modules headless; unit tests
  • comparisons with diff
    • testing a module's promised functionality: each module could offer before/after images as part of their API; by running the module on the before image, you should get exactly the after image, comparing with an image diff

Use cases

  • make an Infragram module that accepts a math expression

Bugs

  • BUG: this doesn't work for defaults: imageboard.loadImage('examples/grid.png', function() {});
    • we should make defaults a config of the first module

Module Candidates

Ideas

Referencing earlier states

Complex sequences with masking could require accessing previous states (or nonlinearity):

  • flood-fill an area
  • select only the flooded area
    • roundabout: lighten everything to <50%, then flood-fill with black? Not 100% reliable.
    • roundabout 2: flood fill, then blink-diff with original
  • then add step which recovers original image, repeat flood-fill/blink-diff for second region
  • reference above masked states in a mask module, with maskModule.draw(image, { getMask: function() { return maskImg } })

Notes:

pattern-fill module to use patterns in JS canvas:

var c=document.getElementById("myCanvas");
var ctx=c.getContext("2d");
var img=document.getElementById("lamp");
var pat=ctx.createPattern(img,"repeat");
ctx.rect(0,0,150,100);
ctx.fillStyle=pat;
ctx.fill();

Masking:

ctx.save();
ctx.beginPath();
ctx.moveTo(0, 0);
ctx.lineTo(160, 600);
ctx.rect(0, 0, 160, 600);
ctx.closePath();
ctx.clip();
ctx.drawImage(img, 0, 0);
ctx.restore();

UI notes:


settings: {
  'threshold': {
    type: 'slider',
    label: 'Threshold',
    default: 50,
    min: 0,
    max: 100
  },
  'colors': {
    type: 'select',
    label: 'Colors',
    options: [
      { name: '0', value: '0', default: true },
      { name: '1', value: '1' },
      { name: '2', value: '2' }
    ]
  }
}

Possible web-based commandline interface: https://hyper.is/?

Path cutting

  • threshold
  • vectorize
    • edge detect
    • direction find (vectorize and colorize)
Description
A pure JavaScript sequential image processing system, inspired by storyboards
Readme GPL-3.0 93 MiB
Languages
JavaScript 99.8%