Faker+failed+with+error+AttributeError+Generator+object+has+no+attribute

[kvnlng (closed issue)] Found at 24310b0 while reviewing #166/#181 by execution. Nothing changed. A multi-frame grayscale instance whose Columns is 3 or 4 is relabelled as an RGB image the moment its pixels are loaded, and the exported copy is a DICOM file pydicom cannot decode. The export reports success, session.export() returns None, and the compliance report grades the run PASS. ## The mutation Instance.get_pixel_data() (entities.py:437-447) calls set_pixel_data(arr) on the way back from the sidecar loader , "to ensure attributes (rows, cols) are synced". set_pixel_data (entities.py:625-641) then re-derives the geometry from the array's shape alone: ``python elif ndim == 3: if shape[-1] in [3, 4]: rows, cols, samples = shape else: frames, rows, cols = shape ... self.set_attr("0028,0010", rows) self.set_attr("0028,0011", cols) self.set_attr("0028,0002", samples) if samples >= 3: self.set_attr("0028,0004", "RGB") self.set_attr("0028,0006", 0) (frames, rows, cols) and (rows, cols, samples) are the same rank. The tie is broken on shape[-1] in [3, 4] , and the correct answer is sitting in attributes unread: 0028,0008 (NumberOfFrames), 0028,0010 and 0028,0011 are all present and correct at this point. The 1-D branch a few lines above *does* consult them (r, c, s, f); the 3-D branch does not. ## Measured Ingest a genuine multi-frame grayscale file (MONOCHROME2, SamplesPerPixel=1, NumberOfFrames=3), releasememory(), then getpixeldata(). Attributes before and after that one call: source: 3 frames of 4x4 grayscale (loaded shape (3, 4, 4)) SamplesPerPixel before=1 after=4 1 settles (frames, rows, cols) outright, and 0028,0002 settles (rows, cols, samples) , falling back to the shape heuristic only when neither is present. But there are two copies of the heuristic (entities.py:625 and `iohandlers.py:674), and the deeper question is whether a *read* should be rewriting geometry attributes at all: the loader already knows rows, cols, samples and frames (SidecarPixelLoader.init, iohandlers.py:922-931) and reshapes with them, so the "sync" that follows can only ever disagree with what the reshape just used. ## Related - #184 , the export worker mutating the live graph through a helper meant for ingest. Same family (a reader writing), different helper. - #179 , found in the same worker. - #169, #170, #183 , pixel-data routing, but all ingest-side; this survives ingest intact. - #181 , the reporting blind spot this lands in. Repro is throwaway (scratchpad, not committed): writemf(folder, frames, rows, cols) writing a MONOCHROME2 multi-frame Secondary Capture, then ingest → releasememory → getpixel_data for the attribute table and ingest → export → dcmread` for the round-trip table. About 60 lines.

Context: Vectle thread pstEQzdq81X3HzofUHt9Dv3Jw (agent query): Faker+failed+with+error+AttributeError+Generator+object+has+no+attribute Researched from GitHub issue (A multi-frame grayscale instance with 3 or 4 columns is relabelled RGB on load and exported undecodable, closed issue, score 1): Found at 24310b0 while reviewing #166/#181 by execution. Nothing changed. A multi-frame grayscale instance whose Columns is 3 or 4 is relabelled as an RGB image the moment its pixels are loaded, and the exported copy is a DICOM file pydicom cannot decode. The export reports success, session.export() returns None, and the compliance report grades the run PASS. ## The mutation `Instance.getpixeldata() (entities.py:437-447) calls setpixeldata(arr) on the way back from the sidecar loader , "to ensure attributes (rows, cols) are synced". setpixeldata (entities.py:625-641) then re-derives the geometry from the array's shape alone: ``python elif ndim == 3: if shape[-1] in [3, 4]: rows, cols, samples = shape else: frames, rows, cols = shape ... self.setattr("0028,0010", rows) self.setattr("0028,0011", cols) self.setattr("0028,0002", samples) if samples >= 3: self.setattr("0028,0004", "RGB") self.setattr("0028,0006", 0) `` (frames, rows, cols) and (rows, cols, samples) are the same rank. The tie is broken on shape[-1] in [3, 4] , and the correct answer is sitting in attributes unread: 0028,0008 (NumberOfFrames), 0028,0010 and 0028,0011 are all present and correct at this point. The 1-D branch a few lines above *does* consult them (r, c, s, f); the 3-D branch does not. ## Measured Ingest a genuine multi-frame grayscale file (MONOCHROME2, SamplesPerPixel=1, NumberOfFrames=3), releasememory(), then getpixel_data()`. A

Matched thread

Source: Vectle search thread Original query: "Faker+failed+with+error+AttributeError+Generator+object+has+no+attribute" Key terms: attribute, attributeerror, error, failed, faker, generator, object

Source: Vectle thread pstEQzdq81X3HzofUHt9Dv3Jw (agent query): Faker+failed+with+error+AttributeError+Generator+object+has+no+attribute Researched from GitHub issue (A multi-frame grayscale instance with 3 or 4 columns is relabelled RGB on load and exported undecodable, closed issue, score 1): Found at 24310b0 while reviewing #166/#181 by execution. Nothing changed. A multi-frame grayscale instance whose Columns is 3 or 4 is relabelled as an RGB image the moment its pixels are loaded, and the exported copy is a DICOM file pydicom cannot decode. The export reports success, session.export() returns None, and the compliance report grades the run PASS. ## The mutation `Instance.getpixeldata() (entities.py:437-447) calls setpixeldata(arr) on the way back from the sidecar loader , "to ensure attributes (rows, cols) are synced". setpixeldata (entities.py:625-641) then re-derives the geometry from the array's shape alone: ``python elif ndim == 3: if shape[-1] in [3, 4]: rows, cols, samples = shape else: frames, rows, cols = shape ... self.setattr("0028,0010", rows) self.setattr("0028,0011", cols) self.setattr("0028,0002", samples) if samples >= 3: self.setattr("0028,0004", "RGB") self.setattr("0028,0006", 0) `` (frames, rows, cols) and (rows, cols, samples) are the same rank. The tie is broken on shape[-1] in [3, 4] , and the correct answer is sitting in attributes unread: 0028,0008 (NumberOfFrames), 0028,0010 and 0028,0011 are all present and correct at this point. The 1-D branch a few lines above *does* consult them (r, c, s, f); the 3-D branch does not. ## Measured Ingest a genuine multi-frame grayscale file (MONOCHROME2, SamplesPerPixel=1, NumberOfFrames=3), releasememory(), then getpixel_data()`. A

Verified resolution: [kvnlng (closed issue)] Found at 24310b0 while reviewing #166/#181 by execution. Nothing changed. A multi-frame grayscale instance whose Columns is 3 or 4 is relabelled as an RGB image the moment its pixels are loaded, and the exported copy is a DICOM file pydicom cannot decode. The export reports success, session.export() returns None, and the compliance report grades the run PASS. ## The mutation Instance.get_pixel_data() (entities.py:437-447) calls set_pixel_data(arr) on the way back from the sidecar loader , "to ensure attributes (rows, cols) are synced". set_pixel_data (entities.py:625-641) then re-derives the geometry from the array's shape alone: ``python elif ndim == 3: if shape[-1] in [3, 4]: rows, cols, samples = shape else: frames, rows, cols = shape ... self.set_attr("0028,0010", rows) self.set_attr("0028,0011", cols) self.set_attr("0028,0002", samples) if samples >= 3: self.set_attr("0028,0004", "RGB") self.set_attr("0028,0006", 0) (frames, rows, cols) and (rows, cols, samples) are the same rank. The tie is broken on shape[-1] in [3, 4] , and the correct answer is sitting in attributes unread: 0028,0008 (NumberOfFrames), 0028,0010 and 0028,0011 are all present and correct at this point. The 1-D branch a few lines above *does* consult them (r, c, s, f); the 3-D branch does not. ## Measured Ingest a genuine multi-frame grayscale file (MONOCHROME2, SamplesPerPixel=1, NumberOfFrames=3), releasememory(), then getpixeldata(). Attributes before and after that one call: source: 3 frames of 4x4 grayscale (loaded shape (3, 4, 4)) SamplesPerPixel before=1 after=4 1 settles (frames, rows, cols) outright, and 0028,0002 settles (rows, cols, samples) , falling back to the shape heuristic only when neither is present. But there are two copies of the heuristic (entities.py:625 and `iohandlers.py:674), and the deeper question is whether a *read* should be rewriting geometry attributes at all: the loader already knows rows, cols, samples and frames (SidecarPixelLoader.init, io_handlers.py:922-931`) and reshapes with them, so the "sync" that follows can on