amide-users Mailing List for AMIDE
Brought to you by:
loening
Menu
▾
▴
amide-users — general discussion and announcement list
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
(2) |
Aug
|
Sep
|
Oct
(2) |
Nov
(3) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(7) |
Feb
|
Mar
(3) |
Apr
(5) |
May
(4) |
Jun
(1) |
Jul
|
Aug
(2) |
Sep
(2) |
Oct
(1) |
Nov
|
Dec
(22) |
| 2004 |
Jan
(16) |
Feb
(12) |
Mar
(11) |
Apr
(3) |
May
(1) |
Jun
(15) |
Jul
(10) |
Aug
(6) |
Sep
(2) |
Oct
(6) |
Nov
(6) |
Dec
(18) |
| 2005 |
Jan
(29) |
Feb
(4) |
Mar
(3) |
Apr
(3) |
May
(4) |
Jun
(16) |
Jul
(11) |
Aug
(10) |
Sep
(8) |
Oct
(3) |
Nov
(7) |
Dec
(9) |
| 2006 |
Jan
(16) |
Feb
(15) |
Mar
(18) |
Apr
(16) |
May
(21) |
Jun
(12) |
Jul
(10) |
Aug
(5) |
Sep
(18) |
Oct
(16) |
Nov
(9) |
Dec
(1) |
| 2007 |
Jan
(5) |
Feb
(8) |
Mar
(2) |
Apr
(7) |
May
(9) |
Jun
(14) |
Jul
(6) |
Aug
(10) |
Sep
(6) |
Oct
(6) |
Nov
(19) |
Dec
(12) |
| 2008 |
Jan
(9) |
Feb
(18) |
Mar
(5) |
Apr
(13) |
May
(2) |
Jun
(1) |
Jul
(4) |
Aug
|
Sep
(4) |
Oct
(3) |
Nov
(6) |
Dec
|
| 2009 |
Jan
(2) |
Feb
(2) |
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
|
Aug
(1) |
Sep
(1) |
Oct
(2) |
Nov
(6) |
Dec
(3) |
| 2010 |
Jan
(6) |
Feb
(5) |
Mar
(2) |
Apr
(4) |
May
(10) |
Jun
(8) |
Jul
(8) |
Aug
(5) |
Sep
(2) |
Oct
(15) |
Nov
|
Dec
(5) |
| 2011 |
Jan
(7) |
Feb
(3) |
Mar
(21) |
Apr
(10) |
May
(4) |
Jun
(2) |
Jul
(7) |
Aug
(12) |
Sep
(4) |
Oct
(1) |
Nov
(4) |
Dec
(13) |
| 2012 |
Jan
|
Feb
(3) |
Mar
(4) |
Apr
(7) |
May
(1) |
Jun
(5) |
Jul
|
Aug
(9) |
Sep
(11) |
Oct
(9) |
Nov
(11) |
Dec
|
| 2013 |
Jan
(2) |
Feb
(5) |
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
(4) |
Aug
(1) |
Sep
(7) |
Oct
(6) |
Nov
(4) |
Dec
(7) |
| 2014 |
Jan
(4) |
Feb
(5) |
Mar
(8) |
Apr
(4) |
May
(2) |
Jun
(6) |
Jul
|
Aug
(2) |
Sep
|
Oct
(4) |
Nov
(2) |
Dec
(2) |
| 2015 |
Jan
(13) |
Feb
(3) |
Mar
(1) |
Apr
(1) |
May
(7) |
Jun
(2) |
Jul
(2) |
Aug
|
Sep
(2) |
Oct
|
Nov
(2) |
Dec
|
| 2016 |
Jan
(1) |
Feb
|
Mar
(4) |
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
(16) |
Feb
(5) |
Mar
(1) |
Apr
(1) |
May
(1) |
Jun
(3) |
Jul
(12) |
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
(1) |
Feb
(1) |
Mar
(4) |
Apr
|
May
(4) |
Jun
|
Jul
(2) |
Aug
|
Sep
(4) |
Oct
|
Nov
(1) |
Dec
|
| 2019 |
Jan
|
Feb
(8) |
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
(4) |
Aug
(5) |
Sep
(1) |
Oct
|
Nov
(3) |
Dec
(4) |
| 2020 |
Jan
(1) |
Feb
(2) |
Mar
(2) |
Apr
(2) |
May
|
Jun
(2) |
Jul
(2) |
Aug
|
Sep
|
Oct
(5) |
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
(1) |
Jun
(2) |
Jul
(2) |
Aug
(1) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
(3) |
Feb
(5) |
Mar
(9) |
Apr
(4) |
May
(3) |
Jun
|
Jul
(1) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2023 |
Jan
|
Feb
|
Mar
(5) |
Apr
|
May
(6) |
Jun
(6) |
Jul
|
Aug
|
Sep
(2) |
Oct
(3) |
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|
From: María Á. P. A. M. <ma...@uc...> - 2024-12-13 14:33:37
|
Hello, good afternoon, I’m Dra. Perez Albacete, I would like information on how to convert DICOM files to XIF in order to use the program. I would like to know which formats are compatible with the program, do you support any intermediate format, for example NIfTI? I look forward to hearing from you thank you very much Best regards -- "Este mensaje es privado y confidencial y se dirige exclusivamente a su destinatario. Si usted recibe este mensaje por error, no debe revelar, distribuir o copiar este e-mail. Por favor, comuníquelo al remitente y borre el mensaje y los archivos adjuntos de su sistema. No hay renuncia a la confidencialidad ni a ningún privilegio a causa de una transmisión errónea o por mal funcionamiento". "This message is private and confidential and it is intended exclusively for the addressee. If your receive this message by mistake, you should not disseminate, distribute or copy this e-mail. Please inform the sender and delete the message and attachments from your system. No confidentiality or any privilege regarding the information is waived or lost by any mistransmission or malfunction". No me imprimas si no es necesario.Don't print me unless it's necessary. |
|
From: Vasilis T. <vth...@gm...> - 2023-10-25 13:44:03
|
Dear all, Thank you for the amazing software. I am using AMIDE on MacOS and everything was running smoothly until I updated to the newest version of MacOS (that is Sonoma 14.0). I am simply wondering if this is something related to the update, and if there is a way to overcome it, other than downgrading to the oldest OS. I would appreciate any input on that. Best regards, Vasilis Theologidis |
|
From: So J. L. <soj...@gm...> - 2023-10-24 13:13:30
|
Hi, I really appreciate you developed and provided this great tool for free to public. I have used Amide with Ventura 13.6 (and the previous OS) with no problem and recently updated my Mac to Sonoma 14. After then I was not able to open Amide with my Mac. Likely Sonoma 14 is conflicting with Amide. Following is the problem that I have: When I clicked Amide app to open, the Amide window popped up and closed in a flash. After I clicked the app to open several more times it showed a message as “AMIDE-bin quit unexpectedly” (screenshot attached). I uninstalled and reinstalled the Amide (amide-1.0.5_osx_64bit_v3) but I still have the same problem. For now, I’m afraid downgrading Sonoma to Ventra would be the only immediate solution to keep using Amide. However it could caused conflict with other apps so before doing that, I wanted to reach out to Amide team for resolving this issue by using Sonoma. Would you please help me to resolve this issue? Best, SJ  |
|
From: ompu72123056 <ompu72123056@s.ompu.ac.jp> - 2023-10-18 10:01:21
|
Dear Sir, My name is Kaoruko Hayashi, a graduate student of Osaka Medical and Pharmaceutical University, Japan. I want to calculate the amount of adipose tissues using CT data. Can the amount of adipose tissues be calculated on CT data using AMIDE software? If YES, I would like to know the method for calculation of the amount of adipose tissues, such as visceral and subcutaneous adipose tissues, on CT values (HU) using AMIDE software. I’m looking forward to hearing from you. Sincerely, Kaoruko ----------------------------------------------------------------- Kaoruko Hayashi Department of Pathobiochemistry Faculty of Pharmacy Osaka Medical and Pharmaceutical University 4-20-1 Nasahara, Takatsuki, Osaka 569-1094, Japan Mail: ompu72123056@s.ompu.ac.jp<mailto:ompu72123056@s.ompu.ac.jp> ----------------------------------------------------------------- |
|
From: Jack <ost...@us...> - 2023-09-15 23:01:07
|
I just installed amide using the AUR PKGBUILD, which is a recipe for source compile. However, launching it gives me (process:5790): GLib-GIO-DEBUG (recursed): Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3) Aborted Is there any further troubleshooting I can do? Thanks for any assistance or suggestions. Jack |
|
From: Du, S. <Shi...@uc...> - 2023-09-07 17:22:17
|
Hi Andy, I was using multiple ROI for one selected dataset. However, the output ROI values were displayed in multiple datasets, including those I did not select before. How should I solve this problem? Thank you very much! Best wishes, Shixian |
|
From: Edmund L. <edm...@pr...> - 2023-06-20 20:25:30
|
Hi! Would suggest to try to open with any other program. Assuming you trying to open DICOM-image - try e.g. FLOSS program [Weasis](https://weasis.org/en/), available also for MS Windows. You can try also [other free Amide alternatives for MS Windows](https://alternativeto.net/software/amide/?feature=dicom-viewer&license=free&platform=windows). Besides, there are also [online DICOM-image viewers](https://duckduckgo.com/?q=online+dicom+viewer) (e.g. https://dicomviewer.net/ , https://thedicomviewer.com/) to quickly check images if size of images and internet connection speed bears to upload them. Then you can at least ensure, whether images itself are fine. If images are damaged, then you can [try to fix them](https://duckduckgo.com/?q=fix+dicom+image). ---- Kind Regards Edmund Laugasson 20.06.23 19:45 Alrakh, Heba: > Hi, > > Unfortunately, I have a problem when I open the saved file from Amide as you can see from the attached picture. Any suggestions? > > And also while I am working on the software all day, sometimes it stops working and close by itself. > > Note: I am using it on WIndoes. > > Best, |
|
From: Alrakh, H. <h.a...@fz...> - 2023-06-20 16:45:33
|
Hi, Unfortunately, I have a problem when I open the saved file from Amide as you can see from the attached picture. Any suggestions? And also while I am working on the software all day, sometimes it stops working and close by itself. Note: I am using it on WIndoes. Best, [cid:eea844c6-6e9c-4b9d-9a60-cb7d5d7db3cc] Heba Alrakh. Institute of Neuroscience and Medicine (INM-4) Forschungszentrum Jülich GmbH 52428 Jülich, Germany Office: 309 Building: 15.2 Tel.: +49 2461/61-96687 eMail: h.a...@fz...<mailto:h.a...@fz...> ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Stefan Müller Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Dr. Ir. Pieter Jansens, Prof. Dr. Astrid Lambrecht, Prof. Dr. Frauke Melchior ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ |
|
From: Edmund L. <edm...@pr...> - 2023-06-14 10:36:02
|
Dear all! [Noticed](https://sourceforge.net/p/amide/mailman/search/?q=package&limit=250), that there are lots of packaging, therefore also installation issues in past. [For Amide GNU/Linux installation I see only RPM-package](https://amide.sourceforge.net/installation_linux.html). Hereby I kindly suggest to use container-based formats as these are independent from system and allow much faster installation: - [Flatpak](https://en.wikipedia.org/wiki/Flatpak) - well known and widely used, very suggested, permissions can be edited with GUI app [Flatseal](https://itsfoss.com/flatseal/) - [AppImage](https://en.wikipedia.org/wiki/AppImage) - this is one file, can be run after downloading from GNU/Linux filesystem and adding executable bit or using AppImage Laucher ([1](https://github.com/TheAssassin/AppImageLauncher), [2](https://appimage.github.io/launcher/)), requires no root permission to run, basically depends only on libc and quite old version - therefore also in older GNU/Linux distros can run E.g. tried to install [Amide in Arch Linux](https://aur.archlinux.org/packages/amide) and ended with endless compiling of different components and in the end got kind of strange error and whole installation interrupted. Then I chose [Weasis](https://weasis.org/en/) as it has [Flatpak version](https://flathub.org/apps/io.github.nroduit.Weasis), which I could install fast and seamlessly. ----- Thank you! |
|
From: MUW <lal...@me...> - 2023-06-13 07:20:55
|
Hi Heba, If you want to access metadata - the easiest is to use ITKsnap, if you want to view the metadata while viewing your pixel data, even then you can’t see every possible metadata. As Andy told, it is easier to view it via dcmtk, commands like dcmdump pretty much spits out all the DICOM metadata. If you use python you can use pydicom and if you use Matlab you can use dcminfo. Hope this helps. Cheers, Lalith > On 12.06.2023, at 16:31, Alrakh, Heba <h.a...@fz...> wrote: > > Dear all, > > Is there a way to access DICOM metadata in Amide? > > Best, > > Heba Alrakh. > Institute of Neuroscience and Medicine (INM-4) > Forschungszentrum Jülich GmbH > 52428 Jülich, Germany > > Office: 309 > Building: 15.2 > > Tel.: +49 2461/61-96687 > eMail: h.a...@fz... <mailto:h.a...@fz...> > > > ------------------------------------------------------------------------------------------------ > ------------------------------------------------------------------------------------------------ > Forschungszentrum Juelich GmbH > 52425 Juelich > Sitz der Gesellschaft: Juelich > Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 > Vorsitzender des Aufsichtsrats: MinDir Stefan Müller > Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), > Karsten Beneke (stellv. Vorsitzender), Dr. Ir. Pieter Jansens, > Prof. Dr. Astrid Lambrecht, Prof. Dr. Frauke Melchior > ------------------------------------------------------------------------------------------------ > ------------------------------------------------------------------------------------------------ > _______________________________________________ > amide-users mailing list > ami...@li... <mailto:ami...@li...> > https://lists.sourceforge.net/lists/listinfo/amide-users |
|
From: Andreas L. <lo...@st...> - 2023-06-12 15:43:26
|
Hi Heba, AMIDE only stores the values it needs when it is reading in the DICOM data. It does not save all the DICOM metadata information. There are command line apps (e.g. DCMTK's tools) for looking at the metadata, and most of the more DICOM centric image viewers that directly use the DICOM data (e.g. Horos, any PACS viewer) have methods of looking at the DICOM headers. Hope that helps, Andy On 2023-06-12 10:31, Alrakh, Heba wrote: > > Dear all, > > > Is there a way to access DICOM metadata in Amide? > > > Best, > > > Heba Alrakh. > > Institute of Neuroscience and Medicine (INM-4) > > Forschungszentrum Jülich GmbH > > 52428 Jülich, Germany > > Office: 309 > > Building: 15.2 > > Tel.: +49 2461/61-96687 > > eMail:h.a...@fz... <mailto:h.a...@fz...> > > > > ------------------------------------------------------------------------------------------------ > ------------------------------------------------------------------------------------------------ > Forschungszentrum Juelich GmbH > 52425 Juelich > Sitz der Gesellschaft: Juelich > Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 > Vorsitzender des Aufsichtsrats: MinDir Stefan Müller > Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), > Karsten Beneke (stellv. Vorsitzender), Dr. Ir. Pieter Jansens, > Prof. Dr. Astrid Lambrecht, Prof. Dr. Frauke Melchior > ------------------------------------------------------------------------------------------------ > ------------------------------------------------------------------------------------------------ > > > _______________________________________________ > amide-users mailing list > ami...@li... > https://lists.sourceforge.net/lists/listinfo/amide-users |
|
From: Alrakh, H. <h.a...@fz...> - 2023-06-12 14:31:46
|
Dear all, Is there a way to access DICOM metadata in Amide? Best, Heba Alrakh. Institute of Neuroscience and Medicine (INM-4) Forschungszentrum Jülich GmbH 52428 Jülich, Germany Office: 309 Building: 15.2 Tel.: +49 2461/61-96687 eMail: h.a...@fz...<mailto:h.a...@fz...> ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Stefan Müller Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Dr. Ir. Pieter Jansens, Prof. Dr. Astrid Lambrecht, Prof. Dr. Frauke Melchior ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ |
|
From: Andreas L. <lo...@st...> - 2023-05-30 13:04:29
|
Hi Heba, The program doesn't display a slice number. Internally, all data is stored as 3D matrices (x, y, and z), so the concept of "slice" isn't used. The z-dimension corresponds to the slice direction, but I think the program only outputs positions to the user as real world values (mm). Andy On 2023-05-26 08:09, Alrakh, Heba wrote: > > Hello, > > > I am using Amide and it is really useful software but I have a question. > > > Is there a way to find out the exact slice number you are on for an > imaging data set when using Amide software? especially when I open a > CT image because the CT has already taken over slices. > > Best, > > > Heba Alrakh. > > Institute of Neuroscience and Medicine (INM-4) > > Forschungszentrum Jülich GmbH > > 52428 Jülich, Germany > > Office: 309 > > Building: 15.2 > > Tel.: +49 2461/61-96687 > > eMail:h.a...@fz... <mailto:h.a...@fz...> > > > > ------------------------------------------------------------------------------------------------ > ------------------------------------------------------------------------------------------------ > Forschungszentrum Juelich GmbH > 52425 Juelich > Sitz der Gesellschaft: Juelich > Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 > Vorsitzender des Aufsichtsrats: MinDir Stefan Müller > Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), > Karsten Beneke (stellv. Vorsitzender), Dr. Ir. Pieter Jansens, > Prof. Dr. Astrid Lambrecht, Prof. Dr. Frauke Melchior > ------------------------------------------------------------------------------------------------ > ------------------------------------------------------------------------------------------------ > > > _______________________________________________ > amide-users mailing list > ami...@li... > https://lists.sourceforge.net/lists/listinfo/amide-users |
|
From: Alrakh, H. <h.a...@fz...> - 2023-05-26 15:09:31
|
Hello, I am using Amide and it is really useful software but I have a question. Is there a way to find out the exact slice number you are on for an imaging data set when using Amide software? especially when I open a CT image because the CT has already taken over slices. Best, Heba Alrakh. Institute of Neuroscience and Medicine (INM-4) Forschungszentrum Jülich GmbH 52428 Jülich, Germany Office: 309 Building: 15.2 Tel.: +49 2461/61-96687 eMail: h.a...@fz...<mailto:h.a...@fz...> ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Stefan Müller Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Dr. Ir. Pieter Jansens, Prof. Dr. Astrid Lambrecht, Prof. Dr. Frauke Melchior ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ |
|
From: Gert V. H. <ger...@xe...> - 2023-05-05 08:08:17
|
Hello, I have two DICOM datasets that contain artificially created spherical objects. The datasets have different voxel sizes (0.1 and 0.4 mm) and their ImagePositionPatient (and ImageOrientationPatient) tags are such that the spheres should be perfectly aligned. When I import them in Amide via DCMTK, they appear to have an offset of 0.15 mm in each dimension (shown in attached PNG). In other viewers (e.g. RadiANT DICOM viewer), the alignment is accurate). Looking at the source code (https://github.com/ferdymercury/amide/blob/main/amide-current/src/dcmtk_interface.cc#L432), it seems that the half-voxel offset could be fixed by uncommenting the three lines of code. Is the mentioned consideration about GE scanner datasets still valid today? If not, it might be good to uncomment the three lines of code? Best regards, Gert |
|
From: Machiel K. <mko...@if...> - 2023-05-04 09:16:22
|
Hi Andy,
Yes, for reasonably sized ROIs (i.e. box shaped), the fractional #voxels
and the sizes of the ROI seem very accurate indeed. But for the 2D
isocontours, it very rapidly goes wrong. By the way, I look at a slice of
only one voxel deep and I check that at least in the Z direction both
images are aligned, so the large discrepancy can only come from the XY
frame. From your words, I take it that with "2D isocontours" the
"fractional voxels" values are probably not so accurate? I have installed
AMIDE with "sudo apt install amide", so I don't have the source code, but I
will try to download it and havce a look.
I deduce from your words that AMIDE is no longer actively in development?
That would be a pity because I find it an extreemly useful software
package.
Cheers,
Machiel
On Wed, May 3, 2023 at 5:13 PM Andreas Loening <lo...@st...> wrote:
> HI Machiel,
>
> It's been about 20 years since I wrote that code.... I think the first
> thing to realize is that every ROI, even a "2D" ROI, is actually 3D. 2D
> just refers to how it's drawn (it's drawn in 2D off the image data, but
> there's some assigned thickness).
>
> The ROI calculation code (if I recall correctly, remember, 20 years) looks
> if the corners of a voxel are within the ROI or not, to decide whether to
> include that voxel in the calculation. If all 8 are in, it's 100% in. To
> increase accuracy, for voxels where only some of the corners are within the
> ROI, it subdivides the voxel (I don't remember if it's 8 or 64 subvoxels,
> but something like that), and assigns these subvoxels as either in or out
> of the ROI. Or maybe it's more simple, and just assigns a fraction of
> number of corners in ROI divided by 8 for the weighting? You'd have to look
> at the code, it's been a while since I wrote this as I said. In any case,
> the ROI is an approximation, and slight shifts in the ROI are going to
> change the number of image space voxels that are being touched. For
> reasonably sized ROI's things will be reasonably accurate.
>
> Andy
>
> On 2023-05-03 06:52, Machiel Kolstein wrote:
>
> Hi,
>
> I have 2 images, with equal pixelsize. It might be that they have slightly
> shifted positions with respect to each other. I create a 2D Isocontour ROI
> on one of them and then apply Tools -> "Calculate ROI statistics".
> Because of the slight shift, I can understand that maybe the #Voxels in
> one image is larger than the other but I would expect the number of
> "Fractional Voxels" to be identical. And certainly the Size should be
> equal. However, this is not the case, even for a ROI with the size of 1
> voxel (which in the other image becomes 1.25 fractional pixel).
> Additionally, when I use a box-shaped ROI ("new_ROI4" in the image of the
> attachment), the Size of the ROI *is* the same for both images. So, the
> Sizes are only different for "2D Isocontour" ROIs. Is there any explanation
> for this?
>
> Cheers,
>
> Machiel
>
>
>
>
> --
> Avís - Aviso - Legal Notice - (LOPD) - http://legal.ifae.es
>
> Avís - Aviso - Legal Notice - (LOPD) - http://legal.ifae.es
>
> _______________________________________________
> amide-users mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/amide-users
>
>
>
--
Avís - Aviso - Legal Notice - (LOPD) - http://legal.ifae.es
--
Avís -
Aviso - Legal Notice - (LOPD) - http://legal.ifae.es
<http://legal.ifae.es/>
|
|
From: Andreas L. <lo...@st...> - 2023-05-03 15:42:17
|
HI Machiel,
It's been about 20 years since I wrote that code.... I think the first
thing to realize is that every ROI, even a "2D" ROI, is actually 3D. 2D
just refers to how it's drawn (it's drawn in 2D off the image data, but
there's some assigned thickness).
The ROI calculation code (if I recall correctly, remember, 20 years)
looks if the corners of a voxel are within the ROI or not, to decide
whether to include that voxel in the calculation. If all 8 are in, it's
100% in. To increase accuracy, for voxels where only some of the corners
are within the ROI, it subdivides the voxel (I don't remember if it's 8
or 64 subvoxels, but something like that), and assigns these subvoxels
as either in or out of the ROI. Or maybe it's more simple, and just
assigns a fraction of number of corners in ROI divided by 8 for the
weighting? You'd have to look at the code, it's been a while since I
wrote this as I said. In any case, the ROI is an approximation, and
slight shifts in the ROI are going to change the number of image space
voxels that are being touched. For reasonably sized ROI's things will be
reasonably accurate.
Andy
On 2023-05-03 06:52, Machiel Kolstein wrote:
> Hi,
>
> I have 2 images, with equal pixelsize. It might be that they have
> slightly shifted positions with respect to each other. I create a 2D
> Isocontour ROI on one of them and then apply Tools -> "Calculate ROI
> statistics".
> Because of the slight shift, I can understand that maybe the #Voxels
> in one image is larger than the other but I would expect the number of
> "Fractional Voxels" to be identical. And certainly the Size should be
> equal. However, this is not the case, even for a ROI with the size of
> 1 voxel (which in the other image becomes 1.25 fractional pixel).
> Additionally, when I use a box-shaped ROI ("new_ROI4" in the image of
> the attachment), the Size of the ROI *is* the same for both images.
> So, the Sizes are only different for "2D Isocontour" ROIs. Is there
> any explanation for this?
>
> Cheers,
>
> Machiel
>
>
>
>
> --
> Avís - Aviso - Legal Notice - (LOPD) - http://legal.ifae.es
>
> Avís - Aviso - Legal Notice - (LOPD) -http://legal.ifae.es
>
>
> _______________________________________________
> amide-users mailing list
> ami...@li...
> https://lists.sourceforge.net/lists/listinfo/amide-users
|
|
From: Machiel K. <mko...@if...> - 2023-05-03 14:52:03
|
Hi,
I have 2 images, with equal pixelsize. It might be that they have slightly
shifted positions with respect to each other. I create a 2D Isocontour ROI
on one of them and then apply Tools -> "Calculate ROI statistics".
Because of the slight shift, I can understand that maybe the #Voxels in one
image is larger than the other but I would expect the number of "Fractional
Voxels" to be identical. And certainly the Size should be equal. However,
this is not the case, even for a ROI with the size of 1 voxel (which in the
other image becomes 1.25 fractional pixel).
Additionally, when I use a box-shaped ROI ("new_ROI4" in the image of the
attachment), the Size of the ROI *is* the same for both images. So, the
Sizes are only different for "2D Isocontour" ROIs. Is there any explanation
for this?
Cheers,
Machiel
--
Avís - Aviso - Legal Notice - (LOPD) - http://legal.ifae.es
--
Avís -
Aviso - Legal Notice - (LOPD) - http://legal.ifae.es
<http://legal.ifae.es/>
|
|
From: Connor <hs...@16...> - 2023-03-24 01:37:18
|
Hello Andy,
Thank you for your reply.
Looks like I got some wrong prompt..............
Best regards,
Connor.
At 2023-03-24 02:21:42, "Andreas Loening" <lo...@st...> wrote:
Hi Connor,
I am not aware of any python module for AMIDE.
Andy
On 3/23/23 12:08 AM, Connor wrote:
Dear AMIDE development team:
I learnt that Amide has a python module? It allows me to control AMIDE programmatically.
but I can't find the python module which is included in the AMIDE software package.
I was very confused because I cannot find this module...
Best regards,
Connor.
_______________________________________________
amide-users mailing list
ami...@li...https://lists.sourceforge.net/lists/listinfo/amide-users
|
|
From: Andreas L. <lo...@st...> - 2023-03-23 18:22:01
|
Hi Connor, I am not aware of any python module for AMIDE. Andy On 3/23/23 12:08 AM, Connor wrote: > > Dear AMIDE development team: > > I learnt that Amide has a python module? It allows me to control AMIDE programmatically. > but I can't find the python module which is included in the AMIDE software package. > I was very confused because I cannot find this module... > Best regards, > Connor. > > > > _______________________________________________ > amide-users mailing list > ami...@li... > https://lists.sourceforge.net/lists/listinfo/amide-users |
|
From: Connor <hs...@16...> - 2023-03-23 07:09:22
|
Dear AMIDE development team: I learnt that Amide has a python module? It allows me to control AMIDE programmatically. but I can't find the python module which is included in the AMIDE software package. I was very confused because I cannot find this module... Best regards, Connor. |
|
From: Andreas L. <lo...@st...> - 2023-03-07 22:03:02
|
Hi Nuria, This program to my knowledge has never been ported to IOS. Andy On 2023-03-05 10:05, Nuria Garcia wrote: > Hi, I'm contacting you because I am having problems during the > installation of Amide on my ipad. Is it possible to install the > application on an iOS system, specifically on an ipad? If so, how can > I do it? Thank you. > > > _______________________________________________ > amide-users mailing list > ami...@li... > https://lists.sourceforge.net/lists/listinfo/amide-users |
|
From: Nuria G. <nur...@ho...> - 2023-03-05 18:05:54
|
Hi, I'm contacting you because I am having problems during the installation of Amide on my ipad. Is it possible to install the application on an iOS system, specifically on an ipad? If so, how can I do it? Thank you. |
|
From: Florian W. <fw...@re...> - 2022-12-03 13:25:46
|
We are trying to build Fedora with a strict(er) C99 compiler, to prepare for upcoming changes in GCC and Clang. <https://fedoraproject.org/wiki/Changes/PortingToModernC> <https://fedoraproject.org/wiki/Toolchain/PortingToModernC> The patch below is required to build volpack with a compiler that rejects implicit function declartions and implicit ints (C language features that were removed in 1999). The patch includes system C headers unconditionally, under the assumption that these days, they are always available. Likewise, function declarations with prototypes are used. There should be a better way to supply the required declaration of the write_den function, though (in examples/scalevolume.c). Thanks, Florian diff --git a/examples/classifyvolume.c b/examples/classifyvolume.c index 59e1353ed48cfdd0..2333fe055239f5a5 100644 --- a/examples/classifyvolume.c +++ b/examples/classifyvolume.c @@ -37,6 +37,11 @@ #include "volume.h" +#include <fcntl.h> +#include <string.h> +#include <unistd.h> + +int main(argc, argv) int argc; char **argv; diff --git a/examples/denfile.c b/examples/denfile.c index 91d5ea19d6b52c87..750e9c186d30bcd3 100644 --- a/examples/denfile.c +++ b/examples/denfile.c @@ -8,6 +8,9 @@ #include <stdio.h> #include <stdlib.h> +#include <fcntl.h> +#include <unistd.h> + #ifndef MIN #define MIN(a, b) ((a) > (b) ? (b) : (a)) #endif @@ -18,6 +21,11 @@ #define MAX_READ_SIZE 8192 /* maximum # of bytes per read(2) call */ +int read_bytes(int fd, char *buf, int bytecount); +int read_shorts(int fd, short *sbuf, int shortcount, int swap); +int read_words(int fd, int *wbuf, int wordcount, int swap); +int write_bytes(int fd, char *buf, int bytecount); + /* * read_den * @@ -211,6 +219,7 @@ int xlen, ylen, zlen; /* volume dimensions */ * error or the full number of bytes could not be read. */ +int read_bytes(fd, buf, bytecount) int fd; /* file descriptor to read from */ char *buf; /* memory in which to store data */ @@ -239,6 +248,7 @@ int bytecount; /* number of bytes to read */ * error or the full number of shorts could not be read. */ +int read_shorts(fd, sbuf, shortcount, swap) int fd; /* file descriptor to read from */ short *sbuf; /* memory in which to store data */ @@ -287,6 +297,7 @@ int swap; /* if nonzero then swap bytes */ * error or the full number of words could not be read. */ +int read_words(fd, wbuf, wordcount, swap) int fd; /* file descriptor to read from */ int *wbuf; /* memory in which to store data */ @@ -335,6 +346,7 @@ int swap; /* if nonzero then swap bytes */ * Return value is 1 if the write was succesful or 0 if there was an error. */ +int write_bytes(fd, buf, bytecount) int fd; /* file descriptor to write to */ char *buf; /* memory containing data */ diff --git a/examples/makeoctree.c b/examples/makeoctree.c index b605d26605471f04..dba9e8dd27704415 100644 --- a/examples/makeoctree.c +++ b/examples/makeoctree.c @@ -37,6 +37,10 @@ #include "volume.h" +#include <fcntl.h> +#include <unistd.h> + +int main() { vpContext *vpc; /* rendering context */ diff --git a/examples/makevolume.c b/examples/makevolume.c index 86484584c396e40c..f58c50fde38a23fa 100644 --- a/examples/makevolume.c +++ b/examples/makevolume.c @@ -38,6 +38,9 @@ #include <sys/types.h> #include "volume.h" +#include <fcntl.h> +#include <unistd.h> + int main() { vpContext *vpc; /* rendering context */ diff --git a/examples/rendervolume.c b/examples/rendervolume.c index a2173d30e894cc62..88fe162e8c84e152 100644 --- a/examples/rendervolume.c +++ b/examples/rendervolume.c @@ -38,6 +38,12 @@ #include <string.h> #include "volume.h" +#include <fcntl.h> +#include <unistd.h> + +void StorePGM(char *image, int width, int height, char *filename); + +int main(argc, argv) int argc; char **argv; @@ -210,6 +216,7 @@ char **argv; return(0); } +void StorePGM(image, width, height, filename) char *image; int width, height; diff --git a/examples/scalevolume.c b/examples/scalevolume.c index a326f6aaab140871..0773c7a7d394e7c9 100644 --- a/examples/scalevolume.c +++ b/examples/scalevolume.c @@ -44,8 +44,12 @@ #include <stdlib.h> #include <stdio.h> +#include <string.h> #include <volpack.h> +int write_den(char *filename, unsigned char *, int xlen, int ylen, int zlen); + +int main(argc, argv) int argc; char **argv; diff --git a/src/makeopts.c b/src/makeopts.c index 5cb954b1e7cdf04f..cf7794ed6f2df0c6 100644 --- a/src/makeopts.c +++ b/src/makeopts.c @@ -43,6 +43,7 @@ * Usage: makeopts output_file [compiler_options ...] */ +int main(argc, argv) int argc; char **argv; |
|
From: Andreas L. <lo...@st...> - 2022-08-05 17:12:54
|
Hi Zhao, AMIDE actually doesn't allow direct adjusting of the interface size of the main interface. You can change the "zoom" to make the images smaller or larger and the main window will grow/shrink appropriately. Andy On 2022.08.03 18:21, 王 曌 wrote: > Dear AMIDE development team: > > I'm a AMIDE new user, when I install AMIDE on my computer (OS: UBuntu > 20.04 LTS), I find that I cannot adjust the interface size of the > AMIDE, which is very inconvenient. How can I modify relevant settings？ > I am looking forward to your reply. > > Best Regards > > Zhao Wang > > > > _______________________________________________ > amide-users mailing list > ami...@li... > https://lists.sourceforge.net/lists/listinfo/amide-users |
58 messages has been excluded from this view by a project administrator.
