[Mrtrix-discussion] (no subject)

[J-Donald Tournier]

Hi Hugh,

Not too sure about this one, but assuming everything works fine normally
apart from that one dataset, I'm guessing the 'poly request too large'
might be the clue to what's going on. There's probably some OpenGL limit on
the maximum number of vertices allowed per primitive (in the case of
streamlines, the primitive is a GL_LINE_STRIP). Looks like one of the
tracks is simply too long for your hardware (these limits are typically
hardware and implementation specific).

Assuming this is the problem, I'm not too sure how to handle it. Anything I
can think of works requires tinkering with the streamline data, either to
remove the offending streamline, or to downsample the data so all tracks
have fewer than the maximum number of vertices allowed. Both of these
approaches can be done relatively easily in Matlab using the
read_mrtrix_tracks & write_mrtrix_tracks Matlab functions included in the
Matlab folder of any recent release of MRtrix 0.2, but you'll have to
figure out the details yourself - I simply don't have the time at the
moment...

Hope this helps.

Cheers,
Donald

--
Dr J-Donald Tournier (PhD)

Senior Lecturer, Biomedical Engineering
Division of Imaging Sciences & Biomedical Engineering
King's College London

A: Department of Perinatal Imaging & Health, 1st Floor South Wing, St
Thomas' Hospital, London. SE1 7EH
T: +44 (0)20 7188 7118 ext 53613
W:
http://www.kcl.ac.uk/medicine/research/divisions/imaging/departments/biomedengineering

On 24 Jul 2014 16:57, "Hugh Pemberton" <hughpemberton1 at gmail.com> wrote:

> Hi everyone, i'm getting this error following mrtrix aborting after I try
> to load some sd_prob results over some DWI data, any ideas what's going on?
>
> Gdk-ERROR **: The program 'mrview' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadLength (poly request too large or internal Xlib length
> erro'.
>   (Details: serial 83399 error_code 16 request_code 153 minor_code 2)
>   (Note to programmers: normally, X errors are reported asynchronously;
>    that is, you will receive the error a while after causing it.
>    To debug your program, run it with the --sync command line
>    option to change this behavior. You can then get a meaningful
>    backtrace from your debugger if you break on the gdk_x_error()
> function.)
> aborting...
>
>
> Many thanks and all the best,
> Hugh
>
> _______________________________________________
> Mrtrix-discussion mailing list
> Mrtrix-discussion at www.nitrc.org
> http://www.nitrc.org/mailman/listinfo/mrtrix-discussion
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.nitrc.org/pipermail/mrtrix-discussion/attachments/20140724/620c8def/attachment.html>