There is no compression in this case and this is the same number that
I get with ReAdW and msconvert, I'm just having trouble figuring out
where the network encoding is coming into play in this example.
--
You received this message because you are subscribed to the Google Groups
Actually I think I figured it outin case anyone else out there is
wondering - if you have a c-style char array holding your hex value,
it will be automatically converted to the host endianess when type
casting into an integer. So then the bytes have to be reconverted
again (network to host)
Hey guys,
No bugs here - I just have a question for the mzXML format experts.
I've been trying to learn about the format these days and I'm a little
bit stuck on the data encoding. The mzXML 2.1 specification states
that data should be encoded from IEEE float to Network binary to Base
64, however
Hey Natalie,
The version is TPP v4.2 JETSTREAM rev 0, Build 200902190939 and I run
on Windows XP
Andrej
On Apr 8, 7:14 pm, Natalie Tasman ntas...@systemsbiology.org wrote:
Hello Andrej,
What version of the TPP are you working with, and on what system
(windows, linux, etc.)?
-Natalie
Hi everyone,
I have been trying all morning to get the proteomic pipeline to work
for me, but it keeps giving me the same error msgs. First I tried
using Mascot's export option to directly save the database search
results as a pepXML file so that I could start directly at step 5 of
the TPP and
