StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11724389
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-07-30T15:17:58.170
FavoriteCount
0
LastActivityDate
2012-07-30T15:17:58.170
LastEditDate
LastEditorUserId
0
OwnerUserId
650012
ParentId
11700938
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
<a href="http://opendicom.sourceforge.net/" rel="nofollow">openDICOM.NET</a> is a very simple library for DICOM file processing. The library itself is designed to be relatively platform-agnostic, i.e. it should be possible to build using the .NET Framework as well as Mono in various operating systems. However, out-of-the-box it is not possible to build as a WinRT/Metro library, so unless you have made substantial refactoring I assume that you have compiled the library as a regular C# class library, .NET Framework 4.5? Assuming that you are really developing a Windows WPF or Forms application, and assuming that you have managed to read a DICOM data set using openDICOM.NET, you should then be able to construct a <code>PixelData</code> object: <pre><code>var pixelData = new PixelData(dataset); </code></pre> From the <code>PixelData</code> object you can access the pixel data as arrays of bytes: <pre><code>byte[][] byteArray = pixelData.ToBytesArray(); </code></pre> You then need to transform the byte two-dimensional array into a one-dimensional array that can be used to construct a bitmap image, by using the following properties of the <code>PixelData</code> object: <pre><code>Rows Columns BitsAllocated (BitsStored) </code></pre> In a WPF application you should be able to create a <a href="http://msdn.microsoft.com/en-us/library/system.windows.media.imaging.writeablebitmap.aspx" rel="nofollow">WriteableBitmap</a> object, and in Windows Forms a <a href="http://msdn.microsoft.com/en-us/library/4e7y164x" rel="nofollow">Bitmap</a> object. However, openDICOM.NET has not been maintained for many years, and I would strongly recommend that you use a different, more up-to-date library as the basis for your DICOM processing. For example, please have a look at the light-weight library <a href="http://evildicom.rexcardan.com/" rel="nofollow">Evil DICOM</a>. Here you have ready-made methods for creating a (Windows Forms) <code>Bitmap</code>, simply create a DICOM image object using the file name and immediately access the corresponding bitmap image: <pre><code>var imageMtx = new EvilDicom.Image.ImageMatrix(name_of_dicom_file); var dicomImage = imageMtx.GetImage(slice_numeber); </code></pre> Evil DICOM currently only works for Windows Forms, but it is probably a relatively small effort to refactor the required classes to use WPF instead. Other open-source class libraries worth exploring are <a href="https://github.com/rcd/mdcm" rel="nofollow">mdcm</a> and the more recent <a href="https://github.com/rcd/fo-dicom" rel="nofollow">fo-dicom</a>, both developed by Colby Dillion. At least mdcm provides full WPF support.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POhow to use opendicom.net library for dicom processing
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USAnders Gustafsson
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.