Improve performance by switching to a single array instead of using Arrays of Arrays which are notably slow.

Document CLI usage for global install

Version 6.22.2 of babel-cli just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As babel-cli is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

α, β and γ are combined now (as they are on the original scripts)

Parameterize for the normal (not line-by-line port) SSIM implementation

Webpack beta27 no longer allows omitting '-loader'. This is breaking the build (see here)

Version 3.12.1 of eslint just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As eslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

We should add a contributor license agreement for the project that all contributors can sign off on before their work is accepted. This ensures that project never runs into any licensing, ownership, or liability issues and Oscar can still lead and direct the project like he wants to.

For reference, these are the two most common CLAs I've found:

https://cla.developers.google.com/about/google-individual
https://code.facebook.com/cla/individual

They appear to be virtually identical.

Ubuntu/Canonical's is slightly different, but offers the same legal protection:
https://ubuntu.com/legal/contributors/agreement

Documentation regarding assets is out of date (no longer needs polyfills on old versions of Node).

Update /assets/README.md

Version 4.5.1 of webdriverio just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As webdriverio is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 2.3.3 of webpack just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As webpack is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

I have no idea why... It's fundamentally the same implementation, and I checked all of the values out of rgb2gray and they're positive integers... You'll notice this when you merge the weber ssim and integer rgb2gray together.

Array size is almost always known, these and these jsperf tests suggest moderate to significant gains by preallocating memory for arrays.

Version 3.15.0 of eslint just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As eslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 3.19.0 of eslint just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As eslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Web tests are very slow to load images, add more tests with small images so testing is more comprehensive without affecting performance

Unlock dependencies from package.json and .npmrc it may also be a good time to add semantic-release

SauceLabs keeps timing out and it's all flukes (tests pass when manually exploring the session). This ticket is to make web tests more resilient

Generate and publish additional builds:

• mx as an isomorphic build (works on node and on the browser) with no external dependencies that takes 3D matrices as input representing the images.
• web as a browser-specific build that relies on the canvas element to retrieve the pixel matrices. It accepts URLs but it's subject to CORS restrictions.

That would be in addition to the current node build that would then be defined as:

• node as a node-specific build that uses node-canvas to retrieve the 3D pixel matrix from each image and accepts Buffer, URLs or a file system path as inputs (current build)

Version 3.5.4 of jsdoc just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As jsdoc is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 2.5.0 of core-js just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As core-js is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Hello,

I'm trying to compute IW-SSIM of two images with size of 2048x4096, but I'm getting this message instead, and the iw-ssim value = -inf

Image size too small for 5 scale IW-SSIM evaluation

Version 2.2.16 of ngrok just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As ngrok is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 4.0.2 of npm-run-all just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As npm-run-all is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Would you consider adding WebP Image support?

Now I have a scenario to test the stability of mobile devices. The performance requirements are relatively high. It needs to complete 224 wide and high picture detection within 20 ms. can we improve the performance through wasm?

Here are my test results：[macbook pro 2018 chrome]

• Mimic strategy from https://github.com/obartra/ssim-perf-comparison to guarantee that there are no performance regressions
• Add benchmark.js to current performance tests
• Add more performance tests

Right now performance and unit tests are mixed. Performance tests should be moved to a separate folder within /spec and have a separate package.json command to run them

Version 2.9.3 of commitizen just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As commitizen is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

yarn add 'ssim.js'
yarn add v1.5.1
[1/4] 🔍 Resolving packages...
[2/4] 🚚 Fetching packages...
[3/4] 🔗 Linking dependencies...
[4/4] 📃 Building fresh packages...
[1/1] ⠂ canvas: '-Goutput_dir=.' ]
[-/1] ⠂ waiting...
[-/1] ⠂ waiting...
[-/1] ⠂ waiting...
error An unexpected error occurred: "/Users/axzq/essence/qb/qb-h5/node_modules/canvas: Command failed.
Exit code: 1
Command: sh
Arguments: -c node-gyp rebuild
Directory: /Users/axzq/essence/qb/qb-h5/node_modules/canvas
Output:
gyp info it worked if it ends with ok
gyp info using [email protected]
gyp info using [email protected] | darwin | x64
gyp info spawn /usr/local/bin/python2
gyp info spawn args [ '/usr/local/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args 'binding.gyp',
gyp info spawn args '-f',
gyp info spawn args 'make',
gyp info spawn args '-I',
gyp info spawn args '/Users/axzq/essence/qb/qb-h5/node_modules/canvas/build/config.gypi',
gyp info spawn args '-I',
gyp info spawn args '/usr/local/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
gyp info spawn args '-I',
gyp info spawn args '/Users/axzq/.node-gyp/9.11.1/include/node/common.gypi',
gyp info spawn args '-Dlibrary=shared_library',
gyp info spawn args '-Dvisibility=default',
gyp info spawn args '-Dnode_root_dir=/Users/axzq/.node-gyp/9.11.1',
gyp info spawn args '-Dnode_gyp_dir=/usr/local/lib/node_modules/npm/node_modules/node-gyp',
gyp info spawn args '-Dnode_lib_file=/Users/axzq/.node-gyp/9.11.1/<(target_arch)/node.lib',
gyp info spawn args '-Dmodule_root_dir=/Users/axzq/essence/qb/qb-h5/node_modules/canvas',
gyp info spawn args '-Dnode_engine=v8',
gyp info spawn args '--depth=.',
gyp info spawn args '--no-parallel',
gyp info spawn args '--generator-output',
gyp info spawn args 'build',
gyp info spawn args '-Goutput_dir=.' ]
Package cairo was not found in the pkg-config search path.
Perhaps you should add the directory containing cairo.pc' to the PKG_CONFIG_PATH environment variable No package 'cairo' found gyp: Call to './util/has_lib.sh freetype' returned exit status 0 while in binding.gyp. while trying to load binding.gyp gyp ERR! configure error gyp ERR! stack Error: gyp` failed with exit code: 1
gyp ERR! stack at ChildProcess.onCpExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:336:16)
gyp ERR! stack at ChildProcess.emit (events.js:180:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:12)
gyp ERR! System Darwin 17.4.0
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/axzq/essence/qb/qb-h5/node_modules/canvas
gyp ERR! node -v v9.11.1

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Version 0.5.5 of json-loader just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As json-loader is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Hi,

I'm using this lib in a nodejs environment, which means I have no access to the ImageData-class but that is fine since ssim don't use that one. But you are using the type so in order to use this lib with typescript I either need to add "lib": ["DOM"] in my tsconfig.json or copy the type from typescripts dom lib.

Have to consider creating your own type for ImageData and remove the dependency to the DOM?

Thanks for the lib,

https://github.com/blog/1184-contributing-guidelines

Add build id to sauce job status

https://wiki.saucelabs.com/display/DOCS/Test+Configuration+Options#TestConfigurationOptions-BuildNumbers

I have this done, and will generate a pull request when I have a second, but wanted to describe what this does and what the behavior is.

I have an integer rgb calculation that produces values super close to the current floating-point version -- except it's much much faster. It can't however be used as the default/drop-in replacement unless we consider it a breaking change. The reason is that it breaks that rounding on the end to end tests by roughly +/- 0.001.

Formula is --
(77 R + 150G+29*B + 128) >>8.

By itself, without the webassembly extensions, it's so much faster than the rgb calculation for the 256x256 frames goes down to 12ms relative to say 60-70ms. However, it pales compared to the webassembly extension which can do a 1920x1080 frame in 3ms. Basically, I want to incorporate this for gradual drop-in support and automatic acceleration where possible.

Improve performance, potentially by providing an additional method to generate SSIM that's computationally equivalent without being a direct, line-by-line, port.

Measure performance gains of switching to a 1-D Float64Array instead of using Arrays of Arrays which are notably slow. If significant, implement.

That would also make it easier to implement item 4 of the roadmap while preserving the original scripts.

Version 6.25.0 of babel-core just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As babel-core is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 4.5.2 of webdriverio just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As webdriverio is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 6.24.1 of babel-core just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As babel-core is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Placeholder ticket for the new implementation.

Version 6.0.1 of npm-install-version just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As npm-install-version is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 4.1.1 of npm-run-all just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As npm-run-all is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Hi there,

I've added support to the americanexpress/jest-image-snapshot library to use this SSIM library, but am having trouble replicating the behavior of pixelmatch with respect to diffs. Ultimately I want to leverage this SSIM library as a pure/complete alternative to pixelmatch for image comparison. However, when I'm currently lacking the tools (or maybe the know-how) to generate reasonable image diffs.

Last night I wrote an algorithm that would generate a diff image based off of the ssim_map. In essence, it would return an rgba(255,0,0,255*(1-ssim)), or at least that was the intention. However, I quickly found that the aspect ratio in the ssim_map didn't match the aspect ratio found in the image itself the results were a bit confounding.

Do you have a suggestion on how I could implement such functionality? Or in the alternative, do you have any plans to add it to the library?

Thanks,
Dan

Performance would be improved for the 2d convolution (for large kernels). Maybe we could use something like jsfft to not have to implement it directly if it performs well enough.

The default one is 11x11 which should lead to about 2x perf improvement for the 2d convolution n + 2*n*log(n) vs the current n^2.

It may not be worth the added complexity though, measure the contribution of conv2 to the total first since it's been significantly improved already.

Detect box kernels for conv2 and handle that case separately (faster)

• It would improve performance on downsizing originalSsim.js
• It would simplify ssim.js downsizing (properly convolving the box kernel should be faster than convolving the 2 decomposed 1d filters)

V8 will automatically infer the type of arrays and use TypedArrays (instead of []) but the implementation should implicit and not rely on that fact

Hi I'm trying to get this to work with require but currently struggling.

Any help would be really appreciated.

var ssim = require("ssim.js");

ssim("/img1.jpg", "/img2.jpg")
  .then(function(out) {
      console.log("SSIM:", out.mssim, "(", out.performance, "ms)");
    })
    .catch(function(err) {
      console.error("Error generating SSIM", err);
    });

Error:

Error: Module version mismatch. Expected 48, got 51.
    at Error (native)
    at Object.Module._extensions..node (module.js:568:18)
    at Module.load (module.js:456:32)
    at tryModuleLoad (module.js:415:12)
    at Function.Module._load (module.js:407:3)
    at Module.require (module.js:466:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/Users/blah/blah/blah/blah/node_modules/canvas/lib/bindings.js:3:18)
    at Module._compile (module.js:541:32)
    at Object.Module._extensions..js (module.js:550:10)

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

CircleCI using 'master' not configured publish branch (undefined)

Unfortunately this error doesn't have any additional information. Feel free to kindly ask the author of the condition-circle plugin to add more helpful information.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Version 2.4.0 of eslint-plugin-import just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As eslint-plugin-import is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 3.5.0 of webpack just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As webpack is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴