FW: HAWK-POPI Comparison-4

5 views
Skip to first unread message

Efremov Sergei

unread,
Feb 5, 2013, 8:03:28 AM2/5/13
to hawk...@googlegroups.com

 

 

Best regards,

 

Efremov Sergey

Smart Imaging Technologies Co.

 

From: Jones, Peter J [mailto:peter...@aramco.com]
Sent: Tuesday, February 05, 2013 6:40 PM
To: David Weldon
Cc: Efremov Sergei; Jones_...@yahoo.com; Qathami, Salman M
Subject: HAWK-POPI Comparison-4

 

Attached are two tables, one compares the data for sample 35 and 35 from the HAWK with the Weatherford instrument data. 

 

It is very nice to see that the Total Hydrocarbons (THC) for POPI-GU1 and HAWK are very similar. We also see very similar numbers to the individual values of LV, TD, TC, the ratio TD/TC, and Tmin.  Based on what I see here, we should be able to run ALL samples with these parameters and be able to feel confident in our testing results. 

 

The only thing we need to address is the correct generation of the *.csv file.  Upon looking at the data in greater depth, the only problem that appears to be present  in the generation of the *.csv file is the use of a value of “0” for the beginning time-step, instead of using a value that is indicative of the background signal response.  That is, the signal for this example should be something like 59.35104 for the zero time step. By having the “0” value at the beginning time step, GC-ROX assumes all signal over “0” should be integrated in calculating yields, thereby, making all calculations under reprocessing incorrect. 

 

With the Legacy POPI equipment, we also have problems when the area under where a baseline becomes large, it is just not seen that often.  However, baselining all samples consistently would improve results. 

 

 

For example, here a pyrogram from the GC-ROX manual edit module which could be improved with a better baseline:

 

 

Thus, addressing this will be important going forward.

 

Not knowing the process completely, I may get some details wrong, but what we want is the *.csv file to reflect values that are the same as the integrated result of signal – baseline used to calculate the yield.  So, the CSV should either be baselined, or should have the baseline value for GC-ROX to use, or the import/QC process should baseline these correctly. When we made GC-ROX, we did not have all the details because of Weatherford, but now we should be able to get this right.

 

Also attached, please find an Excel spreadsheet for all the data from the F-Well.

 

Best regards,

Pete

 

 

 

  ________________________________  


The contents of this email, including all related responses, files and attachments transmitted with it (collectively referred to as “this Email”), are intended solely for the use of the individual/entity to whom/which they are addressed, and may contain confidential and/or legally privileged information. This Email may not be disclosed or forwarded to anyone else without authorization from the originator of this Email. If you have received this Email in error, please notify the sender immediately and delete all copies from your system. Please note that the views or opinions presented in this Email are those of the author and may not necessarily represent those of Saudi Aramco. The recipient should check this Email and any attachments for the presence of any viruses. Saudi Aramco accepts no liability for any damage caused by any virus/error transmitted by this Email.

Picture (Device Independent Bitmap) 2.jpg
F_Well_Compare_by_Instrument.xlsx
F_Well_Legacy_Data.xlsx

Efremov Sergei

unread,
Feb 5, 2013, 10:52:20 PM2/5/13
to hawk...@googlegroups.com
Picture (Device Independent Bitmap) 2.jpg
F_Well_Compare_by_Instrument.xlsx
F_Well_Legacy_Data.xlsx
Reply all
Reply to author
Forward
0 new messages