ImageJ

ImageJ是一个公共领域的Java图像处理程序,受NIH Image for Macintosh的启发。它可以显示,编辑,分析,处理,保存和打印8位,16位和32位图像。

Github星跟蹤圖

ImageJ是一个公共领域的Java图像处理程序,受NIH Image for Macintosh的启发。它在任何具有Java 1.4或更高版本虚拟机的计算机上作为在线小应用程序或作为可下载应用程序运行。可下载的发行版适用于Windows,Mac OS,Mac OS X和Linux。

它可以显示,编辑,分析,处理,保存和打印8位,16位和32位图像。它可以读取许多图像格式,包括TIFF,GIF,JPEG,BMP,DICOM,FITS和“raw”。它支持“stacks"("堆栈”),一系列共享一个窗口的图像。它是多线程的,因此像图像文件读取这样耗时的操作可以与其他操作并行执行。
它可以计算用户定义选择(区域)的面积和像素值统计。它可以测量距离和角度。它可以创建密度直方图和线轮廓图。它支持标准的图像处理功能,如对比度操作,锐化,平滑,边缘检测和中值滤波。
它执行几何变换,如缩放,旋转和翻转。图像可以放大到32:1,缩小到1:32。所有分析和处理功能可在任何放大倍数下使用。该程序同时支持任意数量的窗口(图像),仅受可用内存的限制。
空间校准可用于以毫米为单位提供真实世界的尺寸测量。 还提供密度或灰度校准。
ImageJ被设计为具有通过Java插件提供可扩展性的开放式架构。 自定义获取,分析和处理插件可以使用ImageJ的内置编辑器和Java编译器开发。 用户编写的插件可以解决几乎任何图像处理或分析问题。
ImageJ正在Mac OS X上使用其内置的编辑器和Java编译器,以及BBEdit编辑器和Ant构建工具开发。 源代码是免费提供的。 作者Wayne Rasband(wayne@codon.nih.gov)在美国马里兰州贝塞斯达国家心理健康研究所的研究服务处(工作)。

主要指標

概覽
名稱與所有者imagej/ImageJ
主編程語言Java
編程語言Shell (語言數: 4)
平台
許可證Other
所有者活动
創建於2011-08-01 12:29:11
推送於2025-04-12 14:40:44
最后一次提交2025-04-12 10:40:14
發布數349
最新版本名稱v1.54p (發布於 )
第一版名稱v1.20 (發布於 )
用户参与
星數640
關注者數48
派生數232
提交數2.6k
已啟用問題?
問題數195
打開的問題數68
拉請求數0
打開的拉請求數6
關閉的拉請求數69
项目设置
已啟用Wiki?
已存檔?
是復刻?
已鎖定?
是鏡像?
是私有?

Image.sc forum

Join the chat at https://gitter.im/imagej/imagej
Open in Gitpod

ImageJ2 is a new version of ImageJ seeking to strengthen
both the software and its community. Internally, it is a total redesign of
ImageJ, but it is backwards compatible with ImageJ 1.x via a "legacy layer" and
features a user interface closely modeled after the original.

Under the hood, ImageJ2 completely isolates the image processing logic from the
graphical user interface (UI), allowing ImageJ2 commands to be used in many
contexts, including headless in the cloud or on a server such as
OMERO, or from within another
application such as KNIME,
Icy or
CellProfiler (a Python application).

ImageJ2 has an N-dimensional data model driven by the powerful
ImgLib2 library, which supports image data expressed in
an extensible set of numeric and non-numeric types, and accessed from an
extensible set of data sources. ImageJ2 is driven by a state-of-the-art,
collaborative development process, including version control, unit testing,
automated builds via a continuous integration system, a bug tracker and more.

We are collaborating closely with related projects including
Fiji, SCIFIO and
OME, and are striving to deliver a coherent
software stack reusable throughout the life sciences community and beyond. For
more details, see the SciJava web site.

For more details on the project, see the ImageJ web site.

LICENSING

ImageJ2 is distributed under a
Simplified BSD License;
for the full text of the license, see
LICENSE.txt.

For the list of developers and contributors, see
the parent POM.

IMAGEJ AS A LIBRARY

From Java

This repository is the master ImageJ application, which brings together all of
ImageJ under the artifact
net.imagej:imagej.
It is the easiest entry point if you are looking to use ImageJ as a library from
your own software. E.g., in your Maven pom.xml:

<parent>
  <groupId>org.scijava</groupId>
  <artifactId>pom-scijava</artifactId>
  <version>16.2.0</version>
</parent>
...
<dependency>
  <groupId>net.imagej</groupId>
  <artifactId>imagej</artifactId>
</dependency>

We recommend inheriting from the
pom-scijava parent, although it is not
required. (If you do not, you will need to include the <version> of ImageJ in
your <dependency> declaration.)

From other languages

  • JavaScript: Use the
    imagej module on npm
    to call ImageJ in-process from node.js code.
  • Python: Use the
    imagej module on pypi
    to call ImageJ in-process or interprocess from Python code.
  • Ruby, R, LLVM and beyond: Use GraalVM
    to combine ImageJ with Truffle-based languages in the same VM,
    with shared objects and memory on a single VM heap.
  • Interprocess: Use the
    ImageJ Server
    to work with ImageJ via a RESTful web services API, between
    processes on the same machine, or between multiple machines.

DEPENDENCIES

This component depends on other, lower level components, each of which lives in
its own repository:

It also includes various "plugin" components at runtime:

See the pom.xml for a complete list of dependencies.

BUGS

For a list of known issues, see the
GitHub issues.

Please report any bugs by following the
instructions online.