DetectorChecker

DetectorChecker: analyzing patterns of defects in detector screens - Published in JOSS (2020)

https://github.com/alan-turing-institute/detectorchecker

Science Score: 98.0%

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

  • CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
    Found .zenodo.json file
  • DOI references
    Found 4 DOI reference(s) in README and JOSS metadata
  • Academic publication links
    Links to: joss.theoj.org, zenodo.org
  • Committers with academic emails
    5 of 8 committers (62.5%) from academic institutions
  • Institutional organization owner
    Organization alan-turing-institute has institutional domain (turing.ac.uk)
  • JOSS paper metadata
    Published in Journal of Open Source Software

Keywords

hut23 hut23-122

Scientific Fields

Sociology Social Sciences - 87% confidence
Last synced: 4 months ago · JSON representation

Repository

Project to develop software to assess developing detector screen damage (Web App based on the original DetectorChecker package)

Basic Info
Statistics
  • Stars: 0
  • Watchers: 13
  • Forks: 1
  • Open Issues: 5
  • Releases: 2
Archived
Topics
hut23 hut23-122
Created over 7 years ago · Last pushed 10 months ago
Metadata Files
Readme License Codemeta

README.md

Archived

This repository is no longer in use.


DetectorChecker

Master: Build Status Develop: Build Status

License: MIT status DOI

Created by: Julia Brettschneider (original R code), Tomas Lazauskas (R package engineering), Oscar Giles (package development) and Wilfrid Kendall (testing and editing).

Overview

DetectorChecker is an R package to aid in the assessment of damage to CT scanners arising from exposure to high energy radiation. While the target application concerns CT scanners, this package can also be used to analyze screen damage arising from other sources.

Installation

To install from github you will need to have the devtools package installed.

In R run one of the following, depending on whether you want to build the package Vignettes, removing the # if you do not have devtools installed:

```

install.packages("devtools")

devtools::install_github("alan-turing-institute/DetectorChecker") ```

If you want to be able to view the DetectorChecker_user-guide Vignette you need to install with:

devtools::install_github("alan-turing-institute/DetectorChecker", build_vignettes = TRUE, build_opts = c("--no-resave-data", "--no-manual"))

Installing with the vignettes may be slow (~10 min)

Development version

```

install.packages("devtools")

devtools::install_github("alan-turing-institute/DetectorChecker", ref = "develop") ```

WebApp

The official release of the DetectorChecker WebApp is hosted at https://detectorchecker.azurewebsites.net.

The source code for the WebApp implementation can be found on GitHub: https://github.com/alan-turing-institute/DetectorCheckerWebApp.

Vignette

The user guide vignette provides detailed instructions for using the package and loading specific examples. Make sure you installed the package including vignette following the instructions above (see use of build_vignettes = TRUE in Section Installation) and then load the package followed by the vignette command:

library(detectorchecker) vignette("DetectorChecker_user-guide", package = "detectorchecker")

Manual

Detailed documentation is provided as a pdf. See also the DetectorChecker_user-guide (large html file, needs download).

Examples

DetectorChecker includes a number of example datasets for five detector types:

  1. Pilatus

  2. PerkinElmer

  3. PerkinElmer Refurbished

  4. PerkinElmer Cropped

  5. Excalibur

To load an example dataset, either call:

``` library(detectorchecker)

Initiate a PerkinElmerFull detector object

detector <- create_detector("PerkinElmerFull")

Path of dataset

filepath <- system.file("extdata", "PerkinElmerFull", "BadPixelMapt1.bpm.xml", package = "detectorchecker")

Load a pixel matrix into the detector object

detector <- loadpixmatrix(detector = detector, filepath = filepath) ```

or load one of the examples by calling:

library(detectorchecker) data(PerkinElmerFull_exp_1)

which creates an appropriate detector module and loads an example pixel dataset.

For see the full list of example datasets call

data(package = "detectorchecker")

Citation

If you use DetectorChecker in your work please cite our package.

BibTeX:

@Misc{, title = {{DetectorChecker}: Assessment of damage to CT scanners}, author = {Tomas Lazauskas and Julia Brettschneider and Oscar Giles and Wilfrid Kendall}, url = {https://github.com/alan-turing-institute/DetectorChecker}, }

Getting help

If you found a bug or need support, please submit an issue here.

How to contribute

We welcome contributions! If you are willing to propose new features or have bug fixes to contribute, please submit a pull request here.

Owner

  • Name: The Alan Turing Institute
  • Login: alan-turing-institute
  • Kind: organization
  • Email: info@turing.ac.uk

The UK's national institute for data science and artificial intelligence.

JOSS Publication

DetectorChecker: analyzing patterns of defects in detector screens
Published
December 22, 2020
Volume 5, Issue 56, Page 2474
Authors
Julia A. Brettschneider ORCID
Department of Statistics, University of Warwick, Coventry, United Kingdom, The Alan Turing Institute, London, United Kingdom
Oscar T. Giles
The Alan Turing Institute, London, United Kingdom
Wilfrid S. Kendall ORCID
Department of Statistics, University of Warwick, Coventry, United Kingdom, The Alan Turing Institute, London, United Kingdom
Tomas Lazauskas
The Alan Turing Institute, London, United Kingdom
Editor
Frederick Boehm ORCID
Tags
XCT bad pixel map defective pixels spatial statistics

CodeMeta (codemeta.json)

{
  "@context": "https://raw.githubusercontent.com/codemeta/codemeta/master/codemeta.jsonld",
  "@type": "Code",
  "author": [
    {
      "@id": "http://orcid.org/0000-0003-1763-466X",
      "@type": "Person",
      "email": "Julia.Brettschneider@warwick.ac.uk",
      "name": "Julia A. Brettschneider",
      "affiliation": "Department of Statistics, University of Warwick, UK"
    },
    {
      "@type": "Person",
      "email": "ogiles@turing.ac.uk",
      "name": "Oscar T. Giles",
      "affiliation": "The Alan Turing Institute, UK"
    },
    {
      "@id": "http://orcid.org/0000-0001-9799-3480",
      "@type": "Person",
      "email": "arfon@github.com",
      "name": "Wilfrid S. Kendall",
      "affiliation": "Department of Statistics, University of Warwick, UK"
    },
    {
      "@type": "Person",
      "email": "tlazauskas@turing.ac.uk",
      "name": "Tomas Lazauskas",
      "affiliation": "The Alan Turing Institute, UK"
    },
    {
      "@type": "Person",
      "email": "moreilly@turing.ac.uk",
      "name": "Martin O'Reilly",
      "affiliation": "The Alan Turing Institute, UK"
    }
  ],
  "identifier": "",
  "codeRepository": "https://github.com/alan-turing-institute/DetectorChecker/",
  "datePublished": "2020-05-19",
  "dateModified": "2020-05-19",
  "dateCreated": "2020-05-19",
  "description": "DetectorChecker is an R package to aid in the assessment of damage to CT scanners arising from exposure to high energy radiation. While the target application concerns CT scanners, this package can also be used to analyze screen damage arising from other sources.",
  "keywords": "detector screen, pixel assessment, point pattern, Poisson point process, complete spatial randomness, intensity map, graphical interaction tests, logistic regression",
  "license": "MIT",
  "title": "DetectorChecker",
  "version": "1.0.2"
}

GitHub Events

Total
Last Year

Committers

Last synced: 5 months ago

All Time
  • Total Commits: 338
  • Total Committers: 8
  • Avg Commits per committer: 42.25
  • Development Distribution Score (DDS): 0.586
Past Year
  • Commits: 1
  • Committers: 1
  • Avg Commits per committer: 1.0
  • Development Distribution Score (DDS): 0.0
Top Committers
Name Email Commits
Oscar Giles o****s@t****k 140
Tomas Lazauskas t****s@t****k 122
Wilfrid Kendall W****l@w****k 55
Julia e****7 13
Frederick Boehm f****m@g****m 3
Tomas Lazauskas t****s@I****l 2
Oscar T Giles o****s@l****k 2
Martin O'Reilly m****y@t****k 1
Committer Domains (Top 20 + Academic)

Issues and Pull Requests

Last synced: 4 months ago

All Time
  • Total issues: 51
  • Total pull requests: 70
  • Average time to close issues: 4 months
  • Average time to close pull requests: 2 days
  • Total issue authors: 7
  • Total pull request authors: 4
  • Average comments per issue: 2.27
  • Average comments per pull request: 0.17
  • Merged pull requests: 69
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 0
  • Pull requests: 0
  • Average time to close issues: N/A
  • Average time to close pull requests: N/A
  • Issue authors: 0
  • Pull request authors: 0
  • Average comments per issue: 0
  • Average comments per pull request: 0
  • Merged pull requests: 0
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
  • OscartGiles (18)
  • tomaslaz (14)
  • ejulia17 (10)
  • WilfridSKendall (5)
  • martintoreilly (2)
  • janfreyberg (1)
  • craddm (1)
Pull Request Authors
  • tomaslaz (39)
  • OscartGiles (28)
  • fboehm (2)
  • WilfridSKendall (1)
Top Labels
Issue Labels
enhancement (3) Information (2) bug (1)
Pull Request Labels

Dependencies

DESCRIPTION cran
  • R >= 3.6.2 depends
  • dbscan >= 1.1 imports
  • dplyr >= 0.8.5 imports
  • hdf5r >= 1.3.2 imports
  • igraph >= 1.2.5 imports
  • plyr >= 1.8.6 imports
  • raster >= 3.1 imports
  • readr >= 1.3.1 imports
  • spatstat >= 1.63 imports
  • tiff >= 0.1 imports
  • tools >= 3.6.2 imports
  • knitr >= 1.28 suggests
  • rmarkdown >= 2.1 suggests
  • roxygen2 >= 7.1.0 suggests
  • testthat >= 2.3.2 suggests