New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SFM example using deprecated code #1040

Closed
alexsavio opened this Issue Apr 30, 2016 · 19 comments

Comments

Projects
None yet
5 participants
@alexsavio

alexsavio commented Apr 30, 2016

The example in: http://nipy.sourceforge.net/dipy/examples_built/sfm_reconst.html#example-sfm-reconst

Is using this code:

import dipy.reconst.peaks as dpp

which is deprecated.

@arokem

This comment has been minimized.

Member

arokem commented Apr 30, 2016

This was fixed here: 171e7b7

@arokem

This comment has been minimized.

Member

arokem commented Apr 30, 2016

How should we propagate this to the website? Cherry pick this commit into maint/0.11.x and rebuild the docs?

@Garyfallidis

This comment has been minimized.

Member

Garyfallidis commented Apr 30, 2016

Yes.

@arokem

This comment has been minimized.

Member

arokem commented Apr 30, 2016

Any idea why it's not already on the website? The updated version of this
tutorial is in the 0.11 release.

On Sat, Apr 30, 2016 at 9:02 AM, Eleftherios Garyfallidis <
notifications@github.com> wrote:

Yes.


You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#1040 (comment)

@Garyfallidis

This comment has been minimized.

Member

Garyfallidis commented Apr 30, 2016

@arokem This looks good to me
http://nipy.org/dipy/examples_built/sfm_reconst.html#example-sfm-reconst

We don't use sourceforge anymore. However it seems sourceforge is still up and not updated to the latest website. Indeed it shows dipy 10.0dev rather than 11 release. See here
http://nipy.sourceforge.net/dipy/examples_built/sfm_reconst.html#example-sfm-reconst
We need to fix that. I am not sure how we can update sourceforge with the correct link. @matthew-brett what is the necessary strategy here? Do we update sourceforge? And if yes how? Or shutdown our sourceforge website?

@alexsavio

This comment has been minimized.

alexsavio commented Apr 30, 2016

IMO if you have the documentation elsewhere already I would only keep one.
Maybe Google sent me to the sourceforge version. I am sorry for the confusion.

@arokem

This comment has been minimized.

Member

arokem commented Apr 30, 2016

No worries. We should probably take down the sourceforge website, and
redirect from that link. @Garyfallidis: do you have the permissions on SF?
Or maybe @matthew-brett can help with that?

On Sat, Apr 30, 2016 at 1:07 PM, Alexandre M. S. notifications@github.com
wrote:

IMO if you have the documentation elsewhere already I would only keep one.
Maybe Google sent me to the sourceforge version. I am sorry for the
confusion.


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#1040 (comment)

@Garyfallidis

This comment has been minimized.

Member

Garyfallidis commented Apr 30, 2016

I have access to the sourceforge login but I want to hear first what Matthew thinks about this. Before making any drastic changes.
@alexsavio use dipy.org from now on. And thank you for reporting this problem. We didn't know that the two websites were not sync.

@Garyfallidis

This comment has been minimized.

Member

Garyfallidis commented Apr 30, 2016

I looked a bit inside sourceforge and didn't find what link I need to update. I 'll wait for feedback from Matthew.

@matthew-brett

This comment has been minimized.

Member

matthew-brett commented Apr 30, 2016

@Garyfallidis

This comment has been minimized.

Member

Garyfallidis commented Apr 30, 2016

Can't find it. Where do I need to go? In each page? Sorry not clear.

@matthew-brett

This comment has been minimized.

Member

matthew-brett commented Apr 30, 2016

I haven't done this for ages, but if you look at the Makefile for the docs, from a few years ago, you'll see the sourceforge lines there. I'm guessing that you can ssh into nipy@web.sourceforge.net and then navigate to the given directory to see the files. I seem to remember that I made a script that went through all the pages and replaced the content with a message and a redirect to the matching github page, but I can't find that script on my laptop at the moment.

@Garyfallidis

This comment has been minimized.

Member

Garyfallidis commented Apr 30, 2016

Hm... I don't know the pass for user nipy. And I have no access using my sourceforge username.

@arokem

This comment has been minimized.

Member

arokem commented May 4, 2016

Any success here? Anything I can do to help?

@Laski

This comment has been minimized.

Laski commented Jun 6, 2016

Hi! I'm new to dipy and I've had some issues with the tutorial until I found that there are two different docs. Any update here should be appreciated by the next ones to come.

@arokem

This comment has been minimized.

Member

arokem commented Jun 6, 2016

@Laski : Thanks for the feedback! Are you referring to the fact that there is one tutorial for reconstruction with SFM and another tutorial for tracking with SFM?

@Laski

This comment has been minimized.

Laski commented Jun 7, 2016

You're welcome! I'm referring to the fact that there are two docs for dipy actually searchable from Google (here vs here), which are for different versions. If you have current (0.11.0) version but get by mistake to the (0.10.0dev) docs there are things that may not work.

@arokem

This comment has been minimized.

Member

arokem commented Jun 7, 2016

Ah yes - that's the sourceforge version mentioned above in this same
thread. Thanks.

@Garyfallidis: any luck taking down the SF pages? As you can see, it's
causing some confusion.

On Tue, Jun 7, 2016 at 8:15 AM, Nahuel Laski notifications@github.com
wrote:

You're welcome! I'm referring to the fact that there are two docs for dipy
actually searchable from Google (here
http://nipy.org/dipy/documentation.html vs here
http://nipy.sourceforge.net/dipy/documentation.html), which are for
different versions. If you have current (0.11.0) version but get by mistake
to the (0.10.0dev) there are things that may not work.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#1040 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AAHPNliKbMTbnTqRXG22dZaL7Ff6hcitks5qJYsRgaJpZM4ITXnX
.

@arokem

This comment has been minimized.

Member

arokem commented Dec 16, 2016

Looks like this has been resolved. Closing

@arokem arokem closed this Dec 16, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment