Blog Archives

TF3.0 – Using Estimated/Semi-Quan Amounts

In certain parts of TraceFinder and LabForms, we had exposed the ability to use estimated amounts of substances that did not have their own calibration curve. This feature goes back to the days of the Incos data systems, circa 1980.

In TF 3.0 we have exposed this capability, to be a bit more friendly to use and to be interactive in the user interface, versus just report generated.

In the following video, you will see where to set a compound to use the estimated feature and how it is displayed throughout the applications with visual clues to help you determine that the results you are observing is a semi-quantitative amount.

If the video is blurry please click the cog wheel at the bottom of the panel and increase the video display resolution.

TF 3.0 has some new homes for some functions previously available

Part of the process of looking at User Interface changes, is being able to make sure that we present a logical way of navigating to things, that we may not use on a regular basis. This makes it easier for the end user to remember where to get to that special function, when they need it.

So in the application we still have many right click options, but we have also moved many of the scattered functions into the menu drop downs.

These changes have come from customer request or questions about where functions are.

So here are the most used functions that are not directly data linked.

If the video is blurry please click the cog wheel at the bottom of the panel and increase the video display resolution.

Associating another batch’s Calibration Curve to the current batch – (Answer to a “Ask A Guru” Question)

I think that the questions below are pretty self explanitory of the feature in the video.

What would you like to know?: Hi, Jamie,

 

Example: A Cal curve batch is acquiring. 

 

Case 1:  I submit a new batch of just patient samples and forget to extend the cal file to those samples.  How do I extend the cal file to those samples w/o pulling them into the Cal Curve batch?

 

Case 2:  I submit a new batch of just patient samples and  extend the cal (with the wrong file) to those samples.  How do I  reprocess with the correct cal file?

Company: TFS

Area Of work: Clinical”

So if you have a batch in flight. You should pause the acquisition while you associate a calibration file. It just makes things cleaner if you have an older system with less RAM.

The video is out of the soon to be released TF 3.0, but if you are using and older version the functionality and menu selections are still the same. Dependant on the resolution setting the last frame may be overlayed with another.

If the video is blurry please click the cog wheel at the bottom of the panel and increase the video display resolution.

Making changes in to the multiple peaks in a compound (Answer to a “Ask A Guru” question)

There are times that a chemist may make a method from a PMD file or from CDS, and things need to be changed.

An istance would be swapping an existing quan peak with its confirming peak, or removing a confirming peak.

These changes while seemingly trivial can be a hassel if you have to do many of them. So the TF team has given these options as right click contect menus to make it easier to perfrom these functions.

Watch the video below to get an idea of how to use these tools.

If the video is blurry please click the cog wheel at the bottom of the panel and increase the video display resolution.

There Can Only Be One… Calibration Point

Even though its the most memorable line from the movie “Highlander”, this statement has come up many times for assays where semi quantitation occurs in screening analysis.

One way to accomplish a rough estimate calculated amount is to use the ability to use a single calibration level for a compound.

When you do this there are two settings in the Method setting that can be used.

Selecting Average RF allows for the average response factor for a calibration curve to be calcualted. If you use cal one point

the response of the point will be compared to the response of the compound in the sample and a rough estimate based on the

average will estimate the calcualted amount.

If using a linear curve and one point, you MUST set the Origin setting to Force. This sets the origin at Zero and draw the curve

the response of the one calibration point. Thereby giving you a curve to estimate the calcualted amount from.

There is a third way using Internal Standards, but we’ll save that for another day.

Method General Setting Page – Hmmm.. I missed that setting

One thing that TF has as part of its DNA is to be flexible. Method development is a complex process and we are always looking at ways to reduce the effort, but to give flexibility in our approach.

One page that has alot of power, but is over looked many times is the General Setting Page.

These settings are the general setting for properties in the method.

These settings overide the default settings in the Application and apply to the Method and consiquently all the data that is processed with the method. These settings can be changed in at both the Master and Local Method levels.

Two points to look at.

1) Mass precision – This applies to all the masses used in producing results. It does not apply to the reporting    properties of thethings like RT, or calcualted amounts.

2) Instrument Method Edit/Update – In the master method you have a copy of the selected instrument method, which the ultimate Master instrument method is located in the Xcaliber/Methods directory. When you select edit, you are editing the copy that is located in the Master Method folder. When you select update you are overwriting the changes you made in the Master Method Copy, to the ultimate Instrument Master method in the Xcaliber/Methods directory. When you use these button in the local method you edit the Local Method copy of the instrument method that was copied to the Local Method directory, and the update button copies those changes to the Master Method instrument method. This isolated the Ultimate Master instrument method from batch level changes that you may not want to be inherited by other Master Methods produced in the furture.