hashmapinc / Drillflow

A dockerized WITSML API Server that is agnostic of the backend.
Apache License 2.0
17 stars 13 forks source link

DEV:LOG:A double query for log is not returning correctly #449

Closed cherrera2001 closed 5 years ago

cherrera2001 commented 5 years ago

Currently for the query

<logs xsi:schemaLocation="http://www.witsml.org/schemas/1series http://www.witsml.org/schemas/1series/obj_log.xsd" version="1.4.1.1" xmlns="http://www.witsml.org/schemas/1series" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> 
  <log uidWell="HM_a0096e5b-27e8-4240-a4ba-1fb3256c86d2" uidWellbore="HM_da71e0a7-6276-4874-9742-c21ce3f3b1b2" uid="HM_713a6c33-5634-40aa-9eea-36696c9babd8"> 
    <nameWell /> 
    <nameWellbore /> 
    <name /> 
    <objectGrowing /> 
    <serviceCompany /> 
    <runNumber /> 
    <pass /> 
    <bhaRunNumber /> 
    <indexType /> 
    <startIndex /> 
    <endIndex /> 
    <startDateTimeIndex /> 
    <endDateTimeIndex /> 
    <direction /> 
    <indexCurve /> 
    <nullValue /> 
    <logCurveInfo uid=""> 
      <mnemonic /> 
      <unit /> 
      <nullValue /> 
      <minIndex uom="" /> 
      <maxIndex uom="" /> 
      <minDateTimeIndex /> 
      <maxDateTimeIndex /> 
      <curveDescription /> 
      <typeLogData /> 
      <axisDefinition /> 
    </logCurveInfo> 
  </log> 
  <log uidWell="HM_a0096e5b-27e8-4240-a4ba-1fb3256c86d2" uidWellbore="HM_da71e0a7-6276-4874-9742-c21ce3f3b1b2" uid="L-12345-log"> 
    <nameWell /> 
    <nameWellbore /> 
    <name /> 
    <objectGrowing /> 
    <serviceCompany /> 
    <runNumber /> 
    <pass /> 
    <bhaRunNumber /> 
    <indexType /> 
    <startIndex /> 
    <endIndex /> 
    <startDateTimeIndex /> 
    <endDateTimeIndex /> 
    <direction /> 
    <indexCurve /> 
    <nullValue /> 
    <logCurveInfo uid=""> 
      <mnemonic /> 
      <unit /> 
      <nullValue /> 
      <minIndex uom="" /> 
      <maxIndex uom="" /> 
      <minDateTimeIndex /> 
      <maxDateTimeIndex /> 
      <curveDescription /> 
      <typeLogData /> 
      <axisDefinition /> 
    </logCurveInfo> 
  </log> 
</logs>

The result is not returning correctly, it returns as:

<logs xsi:schemaLocation="http://www.witsml.org/schemas/131 http://www.witsml.org/schemas/131/obj_log.xsd" version="1.3.1.1" xmlns="http://www.witsml.org/schemas/131" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> 
  <log uid="HM_713a6c33-5634-40aa-9eea-36696c9babd8"> 
    <nameWell>Well HM_a0096e5b-27e8-4240-a4ba-1fb3256c86d2</nameWell> 
    <nameWellbore>HM_da71e0a7-6276-4874-9742-c21ce3f3b1b2</nameWellbore> 
    <name>HM_713a6c33-5634-40aa-9eea-36696c9babd8</name> 
    <serviceCompany>Baker Hughes INTEQ</serviceCompany> 
    <runNumber>12.3</runNumber> 
    <indexType>time</indexType> 
    <indexCurve columnIndex="0">Time</indexCurve> 
    <nullValue>-999.25</nullValue> 
    <logCurveInfo uid=""> 
      <mnemonic /> 
      <unit /> 
      <nullValue /> 
      <minIndex uom="" /> 
      <maxIndex uom="" /> 
      <columnIndex></columnIndex> 
      <curveDescription /> 
      <typeLogData /> 
      <axisDefinition> 
        <order>0</order> 
        <count>0</count> 
        <doubleValues /> 
        <stringValues /> 
      </axisDefinition> 
    </logCurveInfo> 
  </log> 
  <log uid="L-12345-log"> 
    <nameWell>Well HM_a0096e5b-27e8-4240-a4ba-1fb3256c86d2</nameWell> 
    <nameWellbore>HM_da71e0a7-6276-4874-9742-c21ce3f3b1b2</nameWellbore> 
    <name>Log ABC-MD</name> 
    <indexType>depth</indexType> 
    <startIndex uom="m">1000.0</startIndex> 
    <endIndex uom="m">1018.0</endIndex> 
    <indexCurve columnIndex="0">Depth</indexCurve> 
    <logCurveInfo uid=""> 
      <mnemonic /> 
      <unit /> 
      <nullValue /> 
      <minIndex uom="" /> 
      <maxIndex uom="" /> 
      <columnIndex></columnIndex> 
      <curveDescription /> 
      <typeLogData /> 
      <axisDefinition> 
        <order>0</order> 
        <count>0</count> 
        <doubleValues /> 
        <stringValues /> 
      </axisDefinition> 
    </logCurveInfo> 
  </log> 
</logs> 

which is missing all of the log curve info. I suspect something is happening in the merge...but it needs to be investigated.

sukhendumukherjee commented 5 years ago

Its working well.I tested with following set of data and getting all channels back.

log Well Energistics-well-0001 Wellbore Energistics-w1-wellbore-0001 Log_HM_f8aebaa1-b998-4ceb-ae65-b2d8af4761de Well Energistics-well-0001 Wellbore Energistics-w1-wellbore-0001 Log_HM_f8aebaa1-b998-4ceb-ae65-b2d8af4761de ]]>
niaalex commented 5 years ago

This item will go in the PR today/ ETA 6/17 3pm @sukhendumukherjee

sukhendumukherjee commented 5 years ago

Working in DEV need to test in QA