Wellbore DDMS Data Loader issueshttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues2023-09-25T09:50:24Zhttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/62Unable to ingest las file due to "timed out"2023-09-25T09:50:24ZDo DangUnable to ingest las file due to "timed out"I have tried to load a smal las file [7004_a1501_1978_comp.las](/uploads/17208d94f2a737114ca873bd672ab186/7004_a1501_1978_comp.las),
however, It runs into a timed out error.
```
New wellbore IDs: ['osdu:master-data--Wellbore:d6f31332097b...I have tried to load a smal las file [7004_a1501_1978_comp.las](/uploads/17208d94f2a737114ca873bd672ab186/7004_a1501_1978_comp.las),
however, It runs into a timed out error.
```
New wellbore IDs: ['osdu:master-data--Wellbore:d6f31332097b4ce48a0e07fea9c16216']
Recognizing the curve families
New welllog IDs: ['osdu:work-product-component--WellLog:cefeedec213c4cbbbd89665f9e223756']
Ingest failed: 7004_a1501_1978_comp.las (see summary for details)
SUMMARY - files not ingested:
7004_a1501_1978_comp.las (timed out)
```
My deployment
```
"service": "Wellbore DDMS OSDU",
"version": "0.2",
"buildNumber": "local",
"cloudEnvironment": "anthos",
"release": "M20"
```
How can I increase the timeout for loading a las file? or any other solution for this problem?https://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/61Investigate issue from preshipping GC M182023-06-25T11:24:02ZChad LeongInvestigate issue from preshipping GC M18https://community.opengroup.org/osdu/platform/pre-shipping/-/issues/527https://community.opengroup.org/osdu/platform/pre-shipping/-/issues/527https://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/60Unable to ingest a LAS file size of 5 MB using wellbore DDMS - Getting error ...2024-01-25T11:16:40ZDurga Prasad Reddy NadavaluriUnable to ingest a LAS file size of 5 MB using wellbore DDMS - Getting error "413 Request Entity Too Large"When I am trying to ingest a welllog LAS file (size of 4-5 MB) using wellbore DDMS API in Azure M14 environment, I am getting error as "413 Request Entity Too Large". In general log las sizes vary from 2-8 MB.
Is there a size limit to i...When I am trying to ingest a welllog LAS file (size of 4-5 MB) using wellbore DDMS API in Azure M14 environment, I am getting error as "413 Request Entity Too Large". In general log las sizes vary from 2-8 MB.
Is there a size limit to ingesting las files and if yes, how can it be extended?
Attached a dummy LAS file to this issue.
[Dummy_LAS.las](/uploads/87f92bb71570c0fac93b0be6e41c3c59/Dummy_LAS.las)https://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/59LAS loader (Wellbore DDMS) - run time messages2023-06-25T11:24:02ZDebasis ChatterjeeLAS loader (Wellbore DDMS) - run time messages@chad - great improvement with messaging.
I made one pass successfully for existing WellLog WPC record.
A few comments -
1. Fix typo error "Begining" -> :Beginning"
2. Mention rowcount - as read from LAS file for curve data and the same...@chad - great improvement with messaging.
I made one pass successfully for existing WellLog WPC record.
A few comments -
1. Fix typo error "Begining" -> :Beginning"
2. Mention rowcount - as read from LAS file for curve data and the same for output (how many written in Wellbore DDMS).
3. Bonus - this could serve as "unit test". show curve values at certain depth in the file (not the very first or last, somewhere in between) and show equivalent value as seen from Wellbore DDMS.I myself do that spot check when I run this utility as tester.
```
C:\TEMP>wbdutil ingest data --welllog_id osdu:work-product-component--WellLog:b43d82d4b6fa4c7caaf0402f85d9c517 -p "C:\TEMP\7556_l0102_1984_comp.las" -t %OSDUTOKEN% -c %CONFIGPATH%
Begining ingest of LAS file: C:\TEMP\7556_l0102_1984_comp.las
Retrieving well log record and associated information.
Validating LAS file well name and curves against existing well log record.
LAS well name: 7023
Well log record well name: 7023
LAS curves: ['DEPT', 'GR', 'DT', 'RHOB', 'NPHI']
Well log record curves: ['DEPT', 'GR', 'DT', 'RHOB', 'NPHI']
Ingest complete: Data written from 7556_l0102_1984_comp.las to Well Log (osdu:work-product-component--WellLog:b43d82d4b6fa4c7caaf0402f85d9c517).
C:\TEMP>
```https://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/58wbdutil - use associated LAS file that is already available in cloud (OSDU DP...2023-03-06T14:12:42ZDebasis Chatterjeewbdutil - use associated LAS file that is already available in cloud (OSDU DP) for case when we use existing WellLog work-product-componentC:\TEMP>wbdutil ingest data --welllog_id osdu:work-product-component--WellLog:3762da4efdbc44c093cca48c597fb3dc **-p "C:\TEMP\7556_l0102_1984_comp.las"** -t %OSDUTOKEN% -c %CONFIGPATH%
For the above use case, the WellLog WPC will have an...C:\TEMP>wbdutil ingest data --welllog_id osdu:work-product-component--WellLog:3762da4efdbc44c093cca48c597fb3dc **-p "C:\TEMP\7556_l0102_1984_comp.las"** -t %OSDUTOKEN% -c %CONFIGPATH%
For the above use case, the WellLog WPC will have an associated LAS file.
In order to be consistent, it would be useful to retrieve that and use as source LAS file. Hence no need for "-p" file part above.
Then things would be more consistent.
cc @chadhttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/57wbdutil - status message misleading after failure2023-03-15T18:19:01ZDebasis Chatterjeewbdutil - status message misleading after failureSee for example this - The job failed. Yet it says "Ingest complete".
Propose saying "Ingest failed" instead of "Ingest complete".
```
C:\TEMP>wbdutil ingest data --welllog_id osdu:work-product-component--WellLog:77874e51358347b9a5a8a43...See for example this - The job failed. Yet it says "Ingest complete".
Propose saying "Ingest failed" instead of "Ingest complete".
```
C:\TEMP>wbdutil ingest data --welllog_id osdu:work-product-component--WellLog:77874e51358347b9a5a8a4309ef50bfc -p "C:\TEMP\7556_l0102_1984_comp-WDMS.las" -t %OSDUTOKEN% -c %CONFIGPATH%
Data not ingested - LAS file validation failed: Well name associated with well log record does not match well name in LAS file.
Ingest complete: Data written from 7556_l0102_1984_comp-WDMS.las to Well Log (osdu:work-product-component--WellLog:77874e51358347b9a5a8a4309ef50bfc).
```
Another example
```
C:\TEMP>wbdutil ingest data --welllog_id osdu:work-product-component--WellLog:77874e51358347b9a5a8a4309ef50bfc -p "C:\TEMP\7556_l0102_1984_comp-WDMS.las" -t %OSDUTOKEN% -c %CONFIGPATH%
Data not ingested: HTTP error: 401. Calling: 'https://r3m15.preshiptesting.osdu.aws/api/os-wellbore-ddms/ddms/v3/welllogs/osdu:work-product-component--WellLog:77874e51358347b9a5a8a4309ef50bfc'. {"reason":"Access denied","message":"The user is not authorized to perform this action. Invalid token.","status":401}
Ingest complete: Data written from 7556_l0102_1984_comp-WDMS.las to Well Log (osdu:work-product-component--WellLog:77874e51358347b9a5a8a4309ef50bfc).
```https://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/56Well log loader from LAS into Wellbore DDMS - please make error message more ...2023-03-15T18:19:02ZDebasis ChatterjeeWell log loader from LAS into Wellbore DDMS - please make error message more verbose to help troubleshootingWhen running, this gave me the following message.
C:\TEMP>wbdutil ingest data --welllog_id osdu:work-product-component--WellLog:77874e51358347b9a5a8a4309ef50bfc -p "C:\TEMP\7556_l0102_1984_comp-WDMS.las" -t %OSDUTOKEN% -c %CONFIGPATH%
D...When running, this gave me the following message.
C:\TEMP>wbdutil ingest data --welllog_id osdu:work-product-component--WellLog:77874e51358347b9a5a8a4309ef50bfc -p "C:\TEMP\7556_l0102_1984_comp-WDMS.las" -t %OSDUTOKEN% -c %CONFIGPATH%
Data not ingested - LAS file validation failed: **Well name associated with well log record does not match well name in LAS file**.
Ingest complete: Data written from 7556_l0102_1984_comp-WDMS.las to Well Log (osdu:work-product-component--WellLog:77874e51358347b9a5a8a4309ef50bfc).
C:\TEMP>
It would be helpful if it shows both values.
1. What is obtained from work-product-component WellLog record.
2. What is obtained from LAS header
We also know that there is issue with convention LAS header says "**Well**" whereas in OSDU DP wpc WellLog is linked to parent **Wellbore**.
So, even that part can be clarified in error message.
cc @chad for informationhttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/55Error in OsduClient arguments: takes 3 positional arguments but 4 were given2022-11-09T21:25:36ZChad LeongError in OsduClient arguments: takes 3 positional arguments but 4 were given```
__init__() takes 3 positional arguments but 4 were given
Traceback (most recent call last):
File "D:\osdu\osdu-preship-test\wellbore-ddms-data-loader\env\lib\site-packages\knack\cli.py", line 231, in invoke
cmd_result = self.in...```
__init__() takes 3 positional arguments but 4 were given
Traceback (most recent call last):
File "D:\osdu\osdu-preship-test\wellbore-ddms-data-loader\env\lib\site-packages\knack\cli.py", line 231, in invoke
cmd_result = self.invocation.execute(args)
File "D:\osdu\osdu-preship-test\wellbore-ddms-data-loader\env\lib\site-packages\knack\invocation.py", line 223, in execute
cmd_result = parsed_args.func(params)
File "D:\osdu\osdu-preship-test\wellbore-ddms-data-loader\env\lib\site-packages\knack\commands.py", line 146, in __call__
return self.handler(*args, **kwargs)
File "D:\osdu\osdu-preship-test\wellbore-ddms-data-loader\env\lib\site-packages\knack\commands.py", line 253, in _command_handler
result = op(client, **command_args) if client else op(**command_args)
File "D:\osdu\osdu-preship-test\wellbore-ddms-data-loader\env\lib\site-packages\wbdutil\commands\ingest.py", line 32, in wellbore
client = OsduClient(config.base_url, token, config.data_partition_id)
TypeError: __init__() takes 3 positional arguments but 4 were given
```https://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/54No module named 'wbdutil.wrapper' when calling wbdutil2022-11-09T21:25:51ZChad LeongNo module named 'wbdutil.wrapper' when calling wbdutilAs reported by @todaiks and confirmed by @chad .
The 3 folders are not properly bundled into the set up : common, service, wrapper.
```
No module named 'wbdutil.wrapper'
Traceback (most recent call last):
File "D:\osdu\wellbore-ddms-...As reported by @todaiks and confirmed by @chad .
The 3 folders are not properly bundled into the set up : common, service, wrapper.
```
No module named 'wbdutil.wrapper'
Traceback (most recent call last):
File "D:\osdu\wellbore-ddms-data-loader\env\lib\site-packages\knack\cli.py", line 231, in invoke
cmd_result = self.invocation.execute(args)
File "D:\osdu\wellbore-ddms-data-loader\env\lib\site-packages\knack\invocation.py", line 134, in execute
self.commands_loader.load_arguments(command)
File "D:\osdu\wellbore-ddms-data-loader\env\lib\site-packages\wbdutil\wbdutil.py", line 129, in load_arguments
super(DdmsCommandLoader, self).load_arguments(command)
File "D:\osdu\wellbore-ddms-data-loader\env\lib\site-packages\knack\commands.py", line 222, in load_arguments
self.command_table[command].load_arguments()
File "D:\osdu\wellbore-ddms-data-loader\env\lib\site-packages\knack\commands.py", line 104, in load_arguments
cmd_args = self.arguments_loader()
File "D:\osdu\wellbore-ddms-data-loader\env\lib\site-packages\knack\commands.py", line 257, in arguments_loader
return list(extract_args_from_signature(CLICommandsLoader._get_op_handler(operation),
File "D:\osdu\wellbore-ddms-data-loader\env\lib\site-packages\knack\commands.py", line 274, in _get_op_handler
op = import_module(mod_to_import)
File "C:\Python39\lib\importlib\__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 790, in exec_module
File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
File "D:\osdu\wellbore-ddms-data-loader\env\lib\site-packages\wbdutil\commands\parse.py", line 3, in <module>
from ..wrapper.environment_var_helper import EnvironmentVarHelper
ModuleNotFoundError: No module named 'wbdutil.wrapper'
```Grant MarblestoneGrant Marblestonehttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/53Not able to load Welllog Data from LAS file using wbdutil, because of NumberO...2023-01-02T09:32:20ZKamlesh TodaiNot able to load Welllog Data from LAS file using wbdutil, because of NumberOfColumns field for the curve data has been changed to required field while creating the log header.
**wbdutil ingest data --welllog_id "odesprod:work-product-component--WellLog:9aab0457b54b44f3b1f0811aab118561" -p "D:\OSDU\dev\LoadLogData\wellbore-ddms-data-loader-main\test-data\1013_akm11_1978_comp.las" -c %CONFIGPATH% -t %OSDUTOKEN%...
**wbdutil ingest data --welllog_id "odesprod:work-product-component--WellLog:9aab0457b54b44f3b1f0811aab118561" -p "D:\OSDU\dev\LoadLogData\wellbore-ddms-data-loader-main\test-data\1013_akm11_1978_comp.las" -c %CONFIGPATH% -t %OSDUTOKEN%**
HTTP error: 400. Calling: 'https://preship.gcp.gnrg-osdu.projects.epam.com/api/os-wellbore-ddms/ddms/v3/welllogs/odesprod:work-product-component--WellLog:9aab0457b54b44f3b1f0811aab118561/data'. {"detail":"The number of columns for curve(s): {'DEPT': 1, 'GR': 1, 'DT': 1, 'RHOB': 1, 'DRHO': 1, 'NPHI': 1} in the bulk data do(es) not match the 'NumberOfColumns' property value in the WellLog record for CurveID: {'DEPT': None, 'GR': None, 'DT': None, 'RHOB': None, 'DRHO': None, 'NPHI': None} ."}
Traceback (most recent call last):
File "C:\Python38\lib\site-packages\knack\cli.py", line 231, in invoke
cmd_result = self.invocation.execute(args)
File "C:\Python38\lib\site-packages\knack\invocation.py", line 223, in execute
cmd_result = parsed_args.func(params)
File "C:\Python38\lib\site-packages\knack\commands.py", line 146, in __call__
return self.handler(*args, **kwargs)
File "C:\Python38\lib\site-packages\knack\commands.py", line 253, in _command_handler
result = op(client, **command_args) if client else op(**command_args)
File "C:\Python38\lib\site-packages\wbdutil\commands\ingest.py", line 80, in welllog_data
service.ingest_welllog_data(input_path, welllog_id)
File "C:\Python38\lib\site-packages\wbdutil\well_service.py", line 149, in ingest_welllog_data
self._client.add_welllog_data(data, welllog_id)
File "C:\Python38\lib\site-packages\wbdutil\osdu_client.py", line 112, in add_welllog_data
self._send_request_json_response("POST", url, payload, None, headers=headers)
File "C:\Python38\lib\site-packages\wbdutil\osdu_client.py", line 181, in _send_request_json_response
res = self._send_request(method, url, content, json, headers)
File "C:\Python38\lib\site-packages\wbdutil\osdu_client.py", line 193, in _send_request
raise DataLoaderWebResponseError(res.status_code, url, res.text)
wbdutil.osdu_client.DataLoaderWebResponseError: HTTP error: 400. Calling: 'https://preship.gcp.gnrg-osdu.projects.epam.com/api/os-wellbore-ddms/ddms/v3/welllogs/odesprod:work-product-component--WellLog:9aab0457b54b44f3b1f0811aab118561/data'. {"detail":"The number of columns for curve(s): {'DEPT': 1, 'GR': 1, 'DT': 1, 'RHOB': 1, 'DRHO': 1, 'NPHI': 1} **in the bulk data do(es) not match the 'NumberOfColumns' property value in the WellLog record for CurveID: {'DEPT': None, 'GR': None, 'DT': None, 'RHOB': None, 'DRHO': None, 'NPHI': None} ."}**
@debasiscChad LeongChad Leonghttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/52Add Csp Specific prefix in service Url2022-05-31T15:16:11ZShrikant GargAdd Csp Specific prefix in service UrlThere can be a scenario where CSP's are adding extra prefix to their service URL because of some security concerns or API gateway in front and hence It will wrong to assume same base url for all the services followed by the same api cont...There can be a scenario where CSP's are adding extra prefix to their service URL because of some security concerns or API gateway in front and hence It will wrong to assume same base url for all the services followed by the same api context path.
e.g. normal url for workflow service : https://osdu-cpd-osdu.osdu-og-platform-validati-ba8e38d4c011d627379af1a4280c4e35-0000.sjc03.containers.appdomain.cloud/api/workflow/v1/
urls with csp specific variable : https://osdu-cpd-osdu.osdu-og-platform-validati-ba8e38d4c011d627379af1a4280c4e35-0000.sjc03.containers.appdomain.cloud/csp-variable/api/workflow/v1/
This can be configurable and csp can have variable of their own.
- Current nomenclature : `{{csp-base-url}}/{{api-service-context-path}}`
- New nomenclature : `{{csp-base-url}}/{{csp-svc-prefix}}/{{api-service-context-path}}`
The presence of `{{csp-svc-prefix}}` should be configurable and by default should not be there so that it won't break existing code.M12 - Release 0.15Shrikant GargShrikant Garghttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/51Well Log loader from DLIS format2024-03-18T04:26:16ZDebasis ChatterjeeWell Log loader from DLIS formatSimilar to existing LAS loaderSimilar to existing LAS loaderhttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/50Define format for line endings in code2022-05-31T15:15:40ZNiall McDaidDefine format for line endings in codeThere are two types of line endings - "LF" (line feed), "CRLF" (carriage return, line feed)
LF is the default on Unix systems, CRLF is the default on Windows. Our codebase currently uses both and this is causing issues with merge reques...There are two types of line endings - "LF" (line feed), "CRLF" (carriage return, line feed)
LF is the default on Unix systems, CRLF is the default on Windows. Our codebase currently uses both and this is causing issues with merge requests (lots of changes are being shown when in fact the only difference is line endings because different developers have a different setup).
We should choose one format to use, document this in the SMG and if possible, find a way to automate the control of this (so developers don't have to think about it).https://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/49Failed to ingest LAS data when UWI is empty or not present2023-03-15T19:24:31ZDipika KheraFailed to ingest LAS data when UWI is empty or not presentFailed to ingest LAS data using `wbdutil` when Well Name present but UWI is empty.
the one which is not working -
```
WELL. 15/9-F-15 : WELL
UWI. : UNIQUE WELL ID
```
other which is working -
```
WELL . ...Failed to ingest LAS data using `wbdutil` when Well Name present but UWI is empty.
the one which is not working -
```
WELL. 15/9-F-15 : WELL
UWI. : UNIQUE WELL ID
```
other which is working -
```
WELL . NO_15/9-F-5: WELL
UWI . 15/9-F-5: UNIQUE WELL ID
```
**Error Logs:**
![image](/uploads/ac43b2c384455580edfb7bb627ad7a9f/image.png)
FYI: @chadGreg HarrisNiall McDaidGreg Harrishttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/48Restructure repository folder structure2022-03-21T09:44:42ZNiall McDaidRestructure repository folder structurePlaces modules into better defined folders, representing the layers of the application as defined in the SMGPlaces modules into better defined folders, representing the layers of the application as defined in the SMGM11 - Release 0.14Niall McDaidNiall McDaidhttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/47Soft mapping for OSDU Welllog to las file2022-12-13T08:25:26ZGreg HarrisSoft mapping for OSDU Welllog to las fileThis is the complementary change to #45 .
This refactor will allow welllog data downloaded from OSDU to be mapped to a LAS file, using a soft mapping as is now done fro LAS to OSDU data.This is the complementary change to #45 .
This refactor will allow welllog data downloaded from OSDU to be mapped to a LAS file, using a soft mapping as is now done fro LAS to OSDU data.https://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/46Write System Maintenance guide2022-08-23T13:29:50ZGreg HarrisWrite System Maintenance guideWrite System Maintenance guide to support handover of DDMS loader.Write System Maintenance guide to support handover of DDMS loader.Niall McDaidNiall McDaidhttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/45Soft mapping of Las data to osdu wellbore and welllog objects2022-08-23T13:29:50ZGreg HarrisSoft mapping of Las data to osdu wellbore and welllog objectsCurrently the mapping from las files to osdu objects is hard coded. This needs to be soft coded in order to support custom headers.
Data mappings should be read from file and look something like this:
```
{
"kind": "osdu:wks:work-pro...Currently the mapping from las files to osdu objects is hard coded. This needs to be soft coded in order to support custom headers.
Data mappings should be read from file and look something like this:
```
{
"kind": "osdu:wks:work-product-component--WellLog:1.1.0",
"mapping":
{
"acl.viewers": "CONFIG.data_default_viewers",
"acl.owners": "CONFIG.data_default_owners",
"legal.legaltags": "CONFIG.legal_tags",
"legal.otherRelevantDataCountries": "CONFIG.legal_relevant_data_countries",
"legal.status": "CONFIG.legal_status",
"data.ReferenceCurveID": "las.curves[0].mnemonic",
"data.WellboreID": {
"type": "function",
"function": "get_wellbore_id",
"args": []
},
"data.Curves": {
"type": "array",
"source": "las.curves",
"mapping": {
"CurveID": "mnemonic",
"Mnemonic": "mnemonic",
"CurveUnit": {
"type": "function",
"function": "las2osdu_curve_uom_converter",
"args": [
"CONFIG.data_partition_id",
"mnemonic"
]
}
}
}
}
}
```
This is an example of how a mapping from LAS to a welllog could be achieved.
Reverse mappings from OSDU to LAS will be considered in a future change.Greg HarrisGreg Harrishttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/44Exception display improvement2022-12-13T08:25:26ZChad LeongException display improvementWe need to display the error in more user-friendly way to show that this is a 404 error.
```
C:\Project\OSDU\CodeBase\data-ingestion\LAS\wellbore-ddms-data-loader\venv\Scripts\python.exe C:/Project/OSDU/CodeBase/data-ingestion/LAS/wellb...We need to display the error in more user-friendly way to show that this is a 404 error.
```
C:\Project\OSDU\CodeBase\data-ingestion\LAS\wellbore-ddms-data-loader\venv\Scripts\python.exe C:/Project/OSDU/CodeBase/data-ingestion/LAS/wellbore-ddms-data-loader/demo/LAS_Loader_WellboreDDMS.py
Successfully authenticated
(1/6) Parsing Las File for header info...
(2/6) Creating wellbore record from LAS data...
Traceback (most recent call last):
File "C:\Project\OSDU\CodeBase\data-ingestion\LAS\wellbore-ddms-data-loader\demo\LAS_Loader_WellboreDDMS.py", line 92, in <module>
wellbore_id = res.json()["recordIds"][0]
File "C:\Project\OSDU\CodeBase\data-ingestion\LAS\wellbore-ddms-data-loader\venv\lib\site-packages\httpx\_models.py", line 1514, in json
Response: b'<html>\r\n<head><title>404 Not Found</title></head>\r\n<body>\r\n<center><h1>404 Not Found</h1></center>\r\n<hr><center>openresty</center>\r\n</body>\r\n</html>\r\n'
return jsonlib.loads(self.content.decode(encoding), **kwargs)
File "C:\Users\0023OI744\AppData\Local\Programs\Python\Python39\lib\json\__init__.py", line 346, in loads
return _default_decoder.decode(s)
File "C:\Users\0023OI744\AppData\Local\Programs\Python\Python39\lib\json\decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "C:\Users\0023OI744\AppData\Local\Programs\Python\Python39\lib\json\decoder.py", line 355, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
```
Process finished with exit code 1https://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/43Rename 'fileload' command to 'parse' to remove ambiguity2022-08-23T13:29:49ZChad LeongRename 'fileload' command to 'parse' to remove ambiguityThe `lasloader` package has a command line interface called `lascli` which has the general syntax:
* `fileload`: Dry run of the ingest command, instead of uploading data to the OSDU instance it creates json files for the wellbore and we...The `lasloader` package has a command line interface called `lascli` which has the general syntax:
* `fileload`: Dry run of the ingest command, instead of uploading data to the OSDU instance it creates json files for the wellbore and welllog.
The fileload commands parses a LAS file and generates the manifest for users to QC the data.
As a user, this command might imply the action is also loading the data to OSDU instance.
We want to change it to 'parse' for less ambiguity in the action of the command.Niall McDaidNiall McDaid