[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-patch-tracker] [patch #9853] [octave forge] (image) implement ni
From: |
Qianqian Fang |
Subject: |
[Octave-patch-tracker] [patch #9853] [octave forge] (image) implement niftiread, niftiwrite, niftiinfo |
Date: |
Thu, 30 Jan 2020 01:46:26 -0500 (EST) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.130 Safari/537.36 |
Follow-up Comment #8, patch #9853 (project octave):
hi Carnë, you can find .nii or .nii.gz files in many websites,
for example
https://github.com/neurolabusc/MRIcroGL/tree/master/Distro
https://nifti.nimh.nih.gov/pub/dist/data/nifti2/
I also included a few my tools for testing purposes
https://github.com/fangq/jnifti/tree/master/samples/headct
https://github.com/fangq/brain2mesh/tree/be391ecf1d225e9b5b4a4b0cab2078a055774ddd/examples/SPM
I am happy to convert my additional toolboxes into octave-forge packages. I
just need someone to point me to a document regarding the formats for
proposing a new octave-forge package.
to optionally support JNIfTI (JSON/JData based nifti files), my functions
requires JSONLab - not just jsonencode and jsondecode, but
jdataencode/jdatadecode as well as binary JSON (UBJSON) support.
currently, jsonencode/decode was discussed in
https://savannah.gnu.org/bugs/?53100, which does not handle encode/decode
JData formats (http://github.com/fangq/jdata).
in the following week, I may have some free time during the evenings of a
conference, so I will start working on formatting the proposed units into
Octave required comment formats. I will post those when I am done.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/patch/?9853>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/