Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Invalid date error on overlay

See original GitHub issue

Bug Report

Describe the Bug

When loading a new image I get an Invalid date Invalid date overlay instead of the patient data. I’m using v2.

What steps can we follow to reproduce the bug?

Load study using JSON from url param
Example JSON:

{
  "studies": [
    {
      "StudyInstanceUID": "1.2.392.200036.9107.500.111704218022204451",
      "StudyDescription": "DEMO",
      "StudyDate": "20180223",
      "StudyTime": "020423.000000",
      "PatientName": "DEMO  DEMO",
      "PatientId": "DEMO",
      "series": [
        {
          "SeriesDescription": "DEMO",
          "SeriesInstanceUID": "1.2.392.200036.9107.500.220.17042.2018022220070409.122",
          "SeriesDate": "20180223",
          "SeriesTime": "020423.000000",
          "Modality": "CR",
          "instances": [
            {
              "metadata": {
                "Columns": 1430,
                "Rows": 1722,
                "InstanceNumber": 1,
                "AcquisitionNumber": 1,
                "PhotometricInterpretation": "MONOCHROME1",
                "BitsAllocated": 16,
                "BitsStored": 12,
                "PixelRepresentation": 0,
                "SamplesPerPixel": 1,
                "PixelSpacing": [
                  "0.17500000000000",
                  "0.17500000000000 "
                ],
                "HighBit": 11,
                "ImageOrientationPatient": null,
                "ImagePositionPatient": null,
                "FrameOfReferenceUID": null,
                "ImageType": [
                  "ORIGINAL",
                  "PRIMARY"
                ],
                "Modality": "CR",
                "SOPInstanceUID": "1.2.392.200036.9107.500.220.17042.20180222.200704.13701.1",
                "SeriesInstanceUID": "1.2.392.200036.9107.500.220.17042.2018022220070409.122",
                "StudyInstanceUID": "1.2.392.200036.9107.500.111704218022204451"
              },
              "url": "dicomweb://demourl"
            }
          ]
        }
      ]
    }
  ]
}

Issue Analytics

State:
Created 2 years ago
Comments:11

Top GitHub Comments

3reactions

carlo-sivilotticommented, Dec 9, 2021

Caused by cornerstone’s generalStudyModule metaData provider failing to return any of the provided study headers.

Commenting out

  cornerstone.metaData.addProvider(
    metadataProvider.get.bind(metadataProvider),
    9999

in extensions/cornertsone/src/init.js resolved this for me. (further details here)

0reactions

huangji123commented, Jul 17, 2022

Caused by cornerstone’s generalStudyModule metaData provider failing to return any of the provided study headers. Commenting out
  cornerstone.metaData.addProvider(
    metadataProvider.get.bind(metadataProvider),
    9999
in extensions/cornertsone/src/init.js resolved this for me. (further details here)
Solved the issue.

Hello, could you tell me the reason why OHIF displays the garbled Chinese names?

@huangji123 You might also be able to change the priority of the cornerstone provider (e.g. ‘9999’ -> ‘-9999’) to allow the other providers to be responsible for the date fields, while still keeping mpr.

my mpr can't work properly what is wrong with it? MPR still works for me with this provider disabled.

Hello, could you tell me the reason why OHIF displays the garbled Chinese names?

Bug Report

Describe the Bug

When loading a new image I get an Invalid date Invalid date overlay instead of the patient data. I’m using v2.

What steps can we follow to reproduce the bug?

Load study using JSON from url param
Example JSON:

{
  "studies": [
    {
      "StudyInstanceUID": "1.2.392.200036.9107.500.111704218022204451",
      "StudyDescription": "DEMO",
      "StudyDate": "20180223",
      "StudyTime": "020423.000000",
      "PatientName": "DEMO  DEMO",
      "PatientId": "DEMO",
      "series": [
        {
          "SeriesDescription": "DEMO",
          "SeriesInstanceUID": "1.2.392.200036.9107.500.220.17042.2018022220070409.122",
          "SeriesDate": "20180223",
          "SeriesTime": "020423.000000",
          "Modality": "CR",
          "instances": [
            {
              "metadata": {
                "Columns": 1430,
                "Rows": 1722,
                "InstanceNumber": 1,
                "AcquisitionNumber": 1,
                "PhotometricInterpretation": "MONOCHROME1",
                "BitsAllocated": 16,
                "BitsStored": 12,
                "PixelRepresentation": 0,
                "SamplesPerPixel": 1,
                "PixelSpacing": [
                  "0.17500000000000",
                  "0.17500000000000 "
                ],
                "HighBit": 11,
                "ImageOrientationPatient": null,
                "ImagePositionPatient": null,
                "FrameOfReferenceUID": null,
                "ImageType": [
                  "ORIGINAL",
                  "PRIMARY"
                ],
                "Modality": "CR",
                "SOPInstanceUID": "1.2.392.200036.9107.500.220.17042.20180222.200704.13701.1",
                "SeriesInstanceUID": "1.2.392.200036.9107.500.220.17042.2018022220070409.122",
                "StudyInstanceUID": "1.2.392.200036.9107.500.111704218022204451"
              },
              "url": "dicomweb://demourl"
            }
          ]
        }
      ]
    }
  ]
}

Hello, could you tell me the reason why OHIF displays the garbled Chinese names?

Top Results From Across the Web

Resolve Invalid Date Errors

An Invalid Dates category is automatically generated when the correct input format cannot be determined or when a problem arises with the source...

Microsoft Sql Server MS Query Invalid date Format Error

I keep getting this error in my query for my parameter dates. I want to date to be mm/dd/yyyy, but in my table,...

Migration error: "Invalid date literal detected" when reading ...

I'm attempting a migration from MSSQL to MySQL and keep coming across a "Invalid date literal detected" error when reading certain decimal ...

RangeError: invalid date - JavaScript - MDN Web Docs

The JavaScript exception "invalid date" occurs when a string leading to an invalid date has been provided to Date or Date.parse() .

Date picker component

v-date-picker accepts ISO 8601 date strings (YYYY-MM-DD). For more information regarding ISO 8601 and other standards, visit the official ISO (International ...