Right, I've added *.ft* to the NMRPipe format list. (In fact there was a
note in the code that I was waiting for someone to tell me what the
standard was!) As it happens, the only NMRPipe data I seem to have around
is the multi-plane version of a 3D data set, which cannot yet be imported
into Analysis, but presumably it's possible to combine them into a single
3D *.ft3 file, which would make this a more useful format to use.
For information, these file formats are specified in the file_type_dict
variable defined near the top of
python/ccpnmr/analysis/OpenSpectrumPopup.py. There's no customisable way
of adding things except to add them by hand, which of course is not that
great an idea since it would be trampled by the next update, but it could
be useful in extremis.
Wayne
On Fri, 9 Nov 2007, Patrick van der Wel wrote:
> Hello,
>
> I was wondering if it would be possible to add some extension filtering
> to the file open dialog in Analysis. In particular for nmrpipe spectra.
> I realize that there are no official limitations or requirements for
> nmrpipe filenames, but I suspect that most people would follow the
> default patterns that the distributed version of nmrpipe uses: *.ft1 for
> 1Ds, *.ft2 for 2Ds etc.
>
> (Note that nmrDraw has a default list of file extensions (in the file
> selection dialog) that is as follows: *.fid *.ft* *.lp *.dat *.DAT; of
> which I would suggest the *.ft* one to be the most useful for use in
> ccpnmr/analysis)
>
> Keeping the default "All (*)" pattern, but just adding this option in
> the pull-down menu would already be very nice.
>
> Patrick
>
> PS. Is it somehow easy for the end user to modify this, if one has some
> common custom extensions?
>
|