64 Bit Open Source Osirix

[Aaron Boxer]

For those who are interested, there is now a 64 bit, open source 
version of the Osirix viewer software available.  This version uses OpenJPEG 2.0 
(instead of Kakadu), VTK 6.2 and ITK 4.6.  Gone is DICOM print and Papyrus 
support. 

3D MPR and Volume Rendering is broken at the moment, but all 2D functionality seems to be in order. 

Check it out here: 

https://github.com/OpenRadStack/osirix/tree/masterFOSS 

Thanks, 
Aaron 

[simonmd]

This is awesome. Must try it out. Is 3D MPR and Volume Rendering broken due to updating VTK/ITK?

And if you forgive me for asking, but does this make things a bit uncomfortable with Pixmeo?

[Alvaro [Andor]]

On 27/01/14 18:34, simonmd wrote:
> This is awesome. Must try it out. Is 3D MPR and Volume Rendering
> broken due to updating VTK/ITK?
>
> And if you forgive me for asking, but does this make things a bit
> uncomfortable with Pixmeo?

This is following open source licenses. Fork and patch. I see nothing
wrong and some companies (including mine, although not anymore) have
been doing this, which is totally legal, btw. We were way more
uncomfortable with pixmeo long time ago for breaking open source licenses.

Thanks a lot, Aaron.

[Aaron Boxer]

On Mon, Jan 27, 2014 at 12:34 PM, simonmd <sim...@gmail.com> wrote:

This is awesome. Must try it out. Is 3D MPR and Volume Rendering broken due to updating VTK/ITK?

Yes, I believe so.   VTK 6 has changed architecture slightly from 5.8.  ITK I am not as familiar with, but I can't imagine

it will be too difficult to fix.

And if you forgive me for asking, but does this make things a bit uncomfortable with Pixmeo?

its funny, I submitted a post on the Osirix user group about adding openjpeg 2.0, and the moderators posted this. Then I submitted

a post to the dev group about 64 bit - they suppressed this post, and they removed the first post on the user group.

So, they are totally censoring the news groups. What is the best way of letting people know about this? I posted

on comp.protocols.dicom as well.

 

On Friday, January 24, 2014 7:43:08 PM UTC-5, Aaron Boxer wrote:

For those who are interested, there is now a 64 bit, open source 
version of the Osirix viewer software available.  This version uses OpenJPEG 2.0 
(instead of Kakadu), VTK 6.2 and ITK 4.6.  Gone is DICOM print and Papyrus 
support. 

3D MPR and Volume Rendering is broken at the moment, but all 2D functionality seems to be in order. 

Check it out here: 

https://github.com/OpenRadStack/osirix/tree/masterFOSS 

Thanks, 
Aaron 

--
You received this message because you are subscribed to the Google Groups "dcm4che" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.
To post to this group, send email to dcm...@googlegroups.com.
Visit this group at http://groups.google.com/group/dcm4che.
For more options, visit https://groups.google.com/groups/opt_out.

[Simon Rascovsky]

As you are obvously aware from your OpenRadStack github org, dcm4chee, mirth and OsiriX are very frequently used together. Posting in all 3 forums + comp.protocols.dicom must surely get the ball rolling. :)

Simon Rascovsky MD, M.Sc
Coordinador de Investigación
Instituto de Alta Tecnología Médica - IATM

--
You received this message because you are subscribed to a topic in the Google Groups "dcm4che" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dcm4che/1HEpR6DEmP4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to dcm4che+u...@googlegroups.com.

[Alvaro [Andor]]

On 27/01/14 19:44, Aaron Boxer wrote:
> its funny, I submitted a post on the Osirix user group about adding
> openjpeg 2.0, and the moderators posted this. Then I submitted
> a post to the dev group about 64 bit - they suppressed this post, and
> they removed the first post on the user group.

Antoine following the line of work I suffered when asking about the
problems with the open source license. Sigh...

> So, they are totally censoring the news groups. What is the best way
> of letting people know about this? I posted
> on comp.protocols.dicom as well.

I'll forward the info to our OsiriX developer, just in case he's
interested or knows somebody who is. And anyway, I've told my bosses and
I'll keep it in mind, just in case...

[Aaron Boxer]

Yes, the copyright holders need to challenge them on this; if they package GPL code, they need to distribute source, or they are breaking the license agreement.

[Rob McLear]

Is there something I need to modify to build this? Checked out the source, getting failure in building the DCM Framework, and a series of directory not found errors.

Thanks so much for this effort!

On Friday, January 24, 2014 7:43:08 PM UTC-5, Aaron Boxer wrote:

[Aaron Boxer]

Hi Rob,

Sorry, in my haste to get to 64 bit, I have not had time to document how I got this working:

Here is what you need to do; it should just take about an hour to get everything set up correctly:

1) clone my repo into some ROOT directory, giving you ROOT --> osirix folder structure

2) checkout master

3) run "unzip binaries" target

4) clone VTK from github into ROOT:   https://github.com/Kitware/VTK.git

5) use CMAKE to configure VTK (use VTK-build directory, use static libraries, use zlib, use VTK-build as install directory... see http://stackoverflow.com/questions/17329258/how-to-install-vtk-6-1-for-osx-10-8-with-cocoa-xcode-support for more details)

6) build VTK with xcode (64 bit build)

7) run install

8) copy *.a static libraries from build directory into   osirix/binaries/VTKLibs directory

9) clone ITK from github into ROOT:   https://github.com/InsightSoftwareConsortium/ITK.git  

10) build with CMAKE and XCODE (64 bit build), similar to VTK above, except use ITK-install for install directory

11) run install 

12) copy static libraries into osirix/binaries/ITKLibs directory

Now, you should be able to build the osirix 64 bit target. I noticed that xcode 5 is pretty buggy regarding linked libraries: sometimes you have to remove and re-add in order to get it working.

Let me know if I left anything out. Also if anyone has ideas on how to streamline this process, let me know.

Aaron

--

[Aaron Boxer]

OK, this is much easier: I created a separate repo for osirix binaries.

To build, just pull the latest from my osirix rep, then clone my osirixBinaries repo

g...@github.com:OpenRadStack/osirixBinaries.git

rename to Binaries, and move to osirix folder.

Then, simply build osirix xcode proj.

[Aaron Boxer]

I have made some improvements; it should be quite simple to build now:

clone the repo

checkout masterFOSS branch 

$ git submodule init

$ git submodule update

build Osirix target

On Wed, Jan 29, 2014 at 8:17 PM, Rob McLear <robm...@me.com> wrote:

--

[Rob McLear]

Wow, if I put this off another 24 hours you'll have it down to one line… can't wait to have some free time to check it out!

> You received this message because you are subscribed to a topic in the Google Groups "dcm4che" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/dcm4che/1HEpR6DEmP4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to dcm4che+u...@googlegroups.com.

> To post to this group, send email to dcm...@googlegroups.com.
> Visit this group at http://groups.google.com/group/dcm4che.
> For more options, visit https://groups.google.com/groups/opt_out.

Rob

--

robm...@me.com

[Pablo]

First of all, thanks Aaron for easy the 64 Bit Open Source OsiriX.

I've tried to build it, following your last instructions  but I get the following message:

zip error: Nothing to do! (try: zip -qr OsiriX Launcher.app/Contents/Resources/OsiriX Lite.zip . -i OsiriX Lite.app)

Command /bin/sh failed with exit code 12

After I tried to build the All prerequisites target with success, it seems promising!

Pablo

[Aaron Boxer]

Hi Pablo,

Thanks.  I've updated the project - it should build correctly now.

Regards,

Aaron

[Pablo]

Thanks Aaron now it builds correctly!

Pablo

[Aaron Boxer]

Glad to hear.  

By the way, I've opened a github pull request for my changes :) :)

Pull requests can't be censored, and they get emailed out to everyone

who is watching the project.

Cheers,

Aaron

On Sun, Feb 2, 2014 at 11:21 AM, Pablo <saup...@gmail.com> wrote:

Thanks Aaron now it build correctly!

El domingo, 2 de febrero de 2014 01:56:33 UTC+1, Aaron Boxer escribió:

Hi Pablo,

Thanks.  I've updated the project - it should build correctly now.

Regards,

Aaron

On Sat, Feb 1, 2014 at 4:14 AM, Pablo <saup...@gmail.com> wrote:

First of all, thanks Aaron for easy the 64 Bit Open Source OsiriX.

I've tried to build it, following your last instructions  but I get the following message:

zip error: Nothing to do! (try: zip -qr OsiriX Launcher.app/Contents/Resources/OsiriX Lite.zip . -i OsiriX Lite.app)

Command /bin/sh failed with exit code 12

After I tried to build the All prerequisites target with success, it seems promising!

Pablo

El viernes, 31 de enero de 2014 15:46:07 UTC+1, Rob McLear escribió:

Wow, if I put this off another 24 hours you'll have it down to one line… can't wait to have some free time to check it out!

On Jan 30, 2014, at 11:26 PM, Aaron Boxer <box...@gmail.com> wrote:

> I have made some improvements; it should be quite simple to build now:
>
> clone the repo
> checkout masterFOSS branch
>
> $ git submodule init
> $ git submodule update
>
> build Osirix target

--

[Rob McLear]

I finally had a chance to download everything. I cloned the masterFOSS repository, I downloaded OsiriXBinaries, renamed them and moved them. I tried to do git submodule init and git submodule update; there were no errors but there was also no response after the command was entered. Building in Xcode 5 fails with a bunch of decompress errors:

/Users/mclearr/Documents/git/osirix/Decompress.mm:132:3: Use of undeclared identifier 'DJDecoderRegistration'; did you mean 'DJLSDecoderRegistration’?

/Users/mclearr/Documents/git/osirix/Decompress.mm:136:3: Use of undeclared identifier 'DJEncoderRegistration'; did you mean 'DJLSEncoderRegistration’?

/Users/mclearr/Documents/git/osirix/Decompress.mm:137:4: Use of undeclared identifier ‘ECC_lossyRGB'

Thanks for any help you can offer.

Rob

--

robm...@me.com

You received this message because you are subscribed to a topic in the Google Groups "dcm4che" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dcm4che/1HEpR6DEmP4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to dcm4che+u...@googlegroups.com.

[Aaron Boxer]

Hi Rob,

Yeah, git submodules turned out to be a bad idea, because I need to merge with the main Osirix repo,

and it doesn't use submodules.  So I am back to replacing the Binaries folder.

I just verified that a clean clone will build.

Try this:

- do a clean clone of osirix - masterFOSS branch

- do a clean clone of osirixBinaries - master branch

- delete Binaries folder in osirix

- rename osirixBinaries to Binaries, and copy into osirix folder

- build osirix target

If you have any more issue, you can create an issue on my github project - its easier to manage this way.

Cheers,

Aaron

[Aaron Boxer]

By the way, I have been asked to change the name of my executable on this project, to avoid any "legal issues".

So, I will be renaming the project to FOSSiriX.   And removing all references to private companies and proprietary code. 

Yayyyyy!!!!!!!

Aaron

On Thursday, February 13, 2014 6:48:41 PM UTC-5, Rob McLear wrote:

[Simon Rascovsky]

Haha good one!

Simon Rascovsky MD, M.Sc
Coordinador de Investigación
Instituto de Alta Tecnología Médica - IATM

[Rob McLear]

Works! Thanks! 

Rob

--

robm...@me.com

[Craig Dykstra]

I know this is an old thread but you guys should check this out:

http://www.osirixexperts.com/solve-your-osirix-frustrations/ 

OsiriX eXperts recently found a build and code for an open source version of 64-bit OsiriX DICOM viewer 5.9 with working 3D volume rendering.

Compiled version available for free download and code contribution on Github. 

[Craig Dykstra]

We have revived and created a new open-source project based on OsiriX called Horos 

http://www.horosproject.org/

Based on the work and code contributed by Alex Bettarini, we have made available an open-source 64-bit version of the DICOM image viewer. We would love for you to view, download, contribute and participate anyway you could. 

[Rob McLear]

Craig,

This is awesome. Seems stable in my use so far. I am guessing that the code base is still v5.9 of OsiriX?

Thanks,

-Rob

> For more options, visit https://groups.google.com/d/optout.

[Craig Dykstra]

Hey Rob,

Glad to hear it! Yes, the code is still based on OsiriX 5.9. Appreciate your feedback. Stay in touch with us as you continue to use it

Any retweets or mentions are appreciated https://twitter.com/horosproject

Join our google group here too https://groups.google.com/forum/#!forum/horos-project

Kind regards,
Craig Dykstra

cr...@purview.net
410.775.4147

[Alex Bettarini]

If you are a developer you definitely want to contribute to the leading open source 64-bit project, where Alex Bettarini took Aaron Boxer’s work one step further:

https://github.com/bettar/osirix

and for a free download of the pre-built binary

http://bettar.no-ip.org/lxiv/dmg.html

[Rob McLear]

I guess my question is, how and why does this differ from the Horos project, and does it make sense to have two parallel projects running, both of which have the same goals?

-Rob

[Alex Bettarini]

Up until now the Horos project has just "taken" the development done in the LXIV project and remarketed as their own. If you check the features you can verify that they follow up exactly, lagging behind usually by one day. I sincerely doubt that they have any real developers working for them. I agree with you that it doesn't make sense to have two projects with the same goal and I also wonder why the Horos folks felt the need to start up their own replica.

[Rafael Cruz]

Alex, at this moment I would be writing to you a direct message, but you already answered my question.

Although not directly related to dcm4che, OsiriX is extensively used as a viewer coupled with dcm4chee, so I believe it's important to hear Craig's perspective.

I personally would be glad to see our efforts going into the right direction.

--

You received this message because you are subscribed to the Google Groups "dcm4che" group.

To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.

To post to this group, send email to dcm...@googlegroups.com.
Visit this group at http://groups.google.com/group/dcm4che.
For more options, visit https://groups.google.com/d/optout.

--
Rafael Cruz

rfl...@gmail.com

[Craig Dykstra]

Hey guys, thanks for asking. Best way to summarize our position and beliefs in Horos is in the recording from our meet-up yesterday. If you have a moment, take a look. Thanks for supporting open source!

https://youtu.be/pga-TgdGjSQ

- Craig

You received this message because you are subscribed to a topic in the Google Groups "dcm4che" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dcm4che/1HEpR6DEmP4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to dcm4che+u...@googlegroups.com.

To post to this group, send email to dcm...@googlegroups.com.
Visit this group at http://groups.google.com/group/dcm4che.
For more options, visit https://groups.google.com/d/optout.

[Alvaro [Andor]]

Hi everybody,

I'll be watching the meet-up now, but just saying, I would love if you join efforts, community and so on. We don't like Antoinne attitude and manners since two or three years ago and we would like to help a bit on a more open-source proyect. We have several plugins we're willing to open and contribute. I have strong experience supporting servers and hosting.

Notes about the two projects...

LXiV:
(Alex, I'm not 'complaining' but just saying things that could improve)
The problem with LXiV web page is a bit confuse and uses a no-ip that seems to point to a home Internet connection @ Sapporo, which gives a sensation of "non reliability", and I think Google doesn't like no-ip domains much. Also, there is no forum or discussion place.

Horos:
Doesn't state or mention its relationship with LXiV and who's fixing issues (Horos or LXiV?).


I think:

• We should join efforts.
• We should send bugfixes back upstream, to Antoinne. Probably he won't accept them, but it should be public and we should point at them, so it becames obvious for everybody that he's not into open source at all.
• We should be very careful with licenses. I've seen in Horos webpage something about the code being GPLv3. The original code is LGPL and we can't change that, as we aren't the owners. Only the new code can be GPLv3. I haven't seen mentions on the license for the new code @ LXiV.
• We should grow a community. An open one. I've been modded and blocked several times at Osirix forums for asking questions about licenses. And he doesn't answer support questions he doesn't like. Even when we've bought more than 20 MD licenses for our clients.

What do you think?

El 21/03/15 a las 14:41, Craig Dykstra escribió:

--

[Rob McLear]

I agree with everything stated below…

[massimiliano lava]

then there is finally a group of people that still work on the real free and opensource version of osirix!

there is a kind of guide to retrive the source code? 

About an half of all links are broken, i'm downloading Xcode now, for firs time then I'm very very new in programming with OS X

how can I "clone the repo" and all others steps