InterFile 3.3

InterFile 3.3是一种医学图像格式,由ASCII的行政数据和二进制图像数据组成。行政数据保存在.h33文件中,图像数据保存在.i33文件中。文件内容包括 Administrative Data 和 Image Data,类型涵盖Static、ROI、Dynamic、Gated、Tomographic、GSPECT及Curve等。

一、简介

InterFile 3.3医学图像格式(MedCon), 该文件由两部分组成, the administrative data in ASCII and the binary image data. 可以将这两个文件放在一个文件中,但是我们更倾向于将数据分成两个文件。The administrative data in a file with extension ‘.h33’ and the binary data in a file with extension ‘.i33’。

这里写图片描述

二、文件格式

1、ADMINISTRATIVE DATA

a)  The administrative data are only composed of key-value pairs and exist in the form of ASCII text. The administrative data should be terminated with a <Ctrl-Z).

b)  All administrative data are to be supplied in the form of key-value pairs in ASCII with delimiters. A ‘key’ is the name of a parameter taking a specific ‘value’, an example being:
patient name := Elvis Presley <cr><lf>

c)  The maximum permitted number of characters for a key or a value or a comment is 255 characters.

d)  Neither keys nor values are to be treated as case sensitive. The characters <space> <tab> <underscore> <!> may all be treated as white space and ignored.

e)  All relevant keys should be included in the intermediate file. A null value is permitted which will invoke the default where specified. The required keys are preceded by an exclamation mark.

f)  A hole line or key-value pairs may have comments appended to them by preceding the comment with a semicolon <;>.

g)  A required key ("name of data file") is included to point to the image data file, even if the binary data is in the same file of the administrative data.

h)  The two alternate keys ("data starting block") or ("data offset in bytes") are used to indicate the offset of the binary data in the file as specified by the key ("name of data file"). The ("data starting block") represents the offset in number of blocks or 2048 bytes. The use of the key ("data offset in bytes") permits the offset to the binary data to be freely specified.

2、 IMAGE DATA

a)  The order of the pixel data shall increment by column from left to right, and then by row, from top to bottom.

b)  Image data shall be in either bit, signed or unsigned integer format, IEEE floating point format (float or double) or ASCII. When the data pixels are written in ASCII, the text line must not exceed 255 characters.

c)  The default value for the key ("imagedata byte order") is BIGENDIAN, but LITTLEENDIAN is allowed. The byte order must be respected for integer and floating point numbers.

d)  Bit data will stored in a single byte, representing 8 pixel values and ordered such that the most significant bit corresponds to the leftmost pixel.

三、文件内容

1、!INTERFILE

!INTERFILE  := <NULL>
;to indicate that this is an Interfile file

!imaging modality := <ASCII> nucmed
;only nucmed is defined for the purpose of this document

!originating system := <ASCII>
;eg.GAMMA-11, MDS, ADAC, etc.

!version of keys := <Numeric> 3.3
;future versions shall increment

date of keys := <DateFormat> 1996:09:26
;date of version 3.3 in date format

conversion program := <ASCII>
;name of program used

program author := <ASCII>
;your chance of fame and fortune

program version := <Numeric>
;to keep track of conversion programs

program date := <DateFormat>
;date of program

2、!GENERAL DATA

!GENERAL DATA := <NULL>
;required but can be treated as comment

original institution := <ASCII>
;name of hospital etc.

contact person := <ASCII>
;another chance of fame (and fortune?)

data description := <ASCII>
;whatever you want

!data starting block := <Numeric> 0
;the value is the offset in blocks of 2048 bytes in either the
;administrative or the data file depending on the key value for
;name of data file (see below)
|      ;
OR
!data offset in bytes:= <Numeric> 0
;as above but the offset may be specified freely in bytes

!name of data file := <ASCII> <NULL>
;<NULL> if no image data exists
;key is a name of the file where the data are present, either when
;in a separate binary data file, or when in a combined
;administrative/binary data file

patient name := <ASCII>
;last name, first name (recommended)

!patient ID := <ASCII>
;as used in your hospital

patient dob := <DateFormat>
;date of birth

patient sex := <ASCIIlist> Unknown M|F|Unknown
;default is Unknown!

!study ID := <ASCII>
;as local conditions dictate

exam type := <ASCII>
;description of procedure as above

data compression := <ASCII> none
;name of algorithm if present- e.g. JPEG, etc.

data encode := <ASCII> none
;name of method of encoding if present- e.g. uuencode etc.

organ := <ASCII> none
;ENLF: for mapping with DICOM tag (0018,0015) BodyPartExamined

isotope := <ASCII> | <ASCII>/<ASCII> none
;ENLF: for mapping with DICOM radionuclide/radiopharmaceutical entries.

dose := <Numeric> 0
;ENLF: for mapping with DICOM tag (0018,1074) RadionuclideTotalDose [MBq]

3、!GENERAL IMAGE DATA

!GENERAL IMAGE DATA := <NULL>
;again required but treated as comment

!type of data := <ASCIIlist>  Other
   Static|Dynamic|Gated|Tomographic|Curve|ROI|GSPECT|Other
;important - this key is used for many conditionals

!total number of images := <Numeric>
;how many images are there altogether in total in the associated
;data file (for all windows etc.). This overrides any other way of
;calculating the total number of images.

study date := <DateFormat>
;date of the first image included in the data file

study time := <TimeFormat>
;time for the start of first image specified

imagedata byte order := <ASCIIlist> BIGENDIAN
        BIGENDIAN|LITTLEENDIAN
;BIGENDIAN is the default if unspecified

process label := <ASCII> none
;ENLF: for mapping with DICOM tag (0008,103E) SeriesDescription

quantification units := +1.696265e-05
;ENLF: global scale factor for mediman dialect

NUD/rescale slope := +1.696265e-05
;ENLF: global scale factor for NUD systems

NUD/rescale intercept := +0.000000e+00
;ENLF: global scale intercept for NUD systems

number of energy windows := <Numeric> 1
;defaulted to one if unspecified

4、

for ( number of energy windows, energy window)
{
      energy window[<energy window>] := <ASCII>
      ;ASCII text- for example "Tc99m"
      ;t
内容概要:本文详细介绍了一个基于Java和Vue的联邦学习隐私保护推荐系统的设计与实现。系统采用联邦学习架构,使用户数据在本地完成模型训练,仅上传加密后的模型参数或梯度,通过中心服务器进行联邦平均聚合,从而实现数据隐私保护与协同建模的双重目标。项目涵盖完整的系统架构设计,包括本地模型训练、中心参数聚合、安全通信、前后端解耦、推荐算法插件化等模块,并结合差分隐私与同态加密等技术强化安全性。同时,系统通过Vue前端实现用户行为采集与个性化推荐展示,Java后端支撑高并发服务与日志处理,形成“本地训练—参数上传—全局聚合—模型下发—个性化微调”的完整闭环。文中还提供了关键模块的代码示例,如特征提取、模型聚合、加密上传等,增强了项目的可实施性与工程参考价值。 适合人群:具备一定Java和Vue开发基础,熟悉Spring Boot、RESTful API、分布式系统或机器学习相关技术,从事推荐系统、隐私计算或全栈开发方向的研发人员。 使用场景及目标:①学习联邦学习在推荐系统中的工程落地方法;②掌握隐私保护机制(如加密传输、差分隐私)与模型聚合技术的集成;③构建高安全、可扩展的分布式推荐系统原型;④实现前后端协同的个性化推荐闭环系统。 阅读建议:建议结合代码示例深入理解联邦学习流程,重点关注本地训练与全局聚合的协同逻辑,同时可基于项目架构进行算法替换与功能扩展,适用于科研验证与工业级系统原型开发。
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值