dcslagel / las-util-django

LAS (Log Ascii Standard v2.0) web utilities and api in Django web framework : beta-level software

Hi there 👋

---

Current Open Source Activity:

---

• Lasio kinverarity1/lasio : Python Log-Ascii-Standard reader/writer

---

Past Open Source Contributions:

---

Log-Ascii-Standard is a data format used in well logging.

• Wellio.js JustinGOSSED/wellio.js : Javascript Log-Ascii-Standard reader/writer

• DLISIO_Notebooks aruss175/DLISIO_Notebooks : Notebook examples plus a Python DLIS-to-LAS converter

• Alaska FRI-Energy-Analytics/alaska : AlasKA well log LAS file aliaser

• LasCheck MandarJKulkarni/lascheck : Python library for checking conformity of LAS files to standards

---

Code Farm Proprietor:

---

• Code Farm: Code Farm provides software engineering support to small-businesses and non-profits.

las-util-django's Issues

Testing: Add test for file upload

Testing: Add tests for upload messages

Clean up flake8 Errors

cd las-util-django/src/las_util
flake8 *.py

admin.py:1:1: F401 'django.contrib.admin' imported but unused
cntrl.py:22:1: W293 blank line contains whitespace
cntrl.py:46:30: W291 trailing whitespace
cntrl.py:54:80: E501 line too long (82 > 79 characters)
models.py:14:1: E302 expected 2 blank lines, found 1
models.py:19:1: E302 expected 2 blank lines, found 1
models.py:25:1: E302 expected 2 blank lines, found 1
models.py:35:80: E501 line too long (85 > 79 characters)
models.py:37:80: E501 line too long (86 > 79 characters)
serializers.py:12:1: E302 expected 2 blank lines, found 1
serializers.py:18:1: E302 expected 2 blank lines, found 1
urls.py:16:5: E265 block comment should start with '# '
urls.py:18:5: E265 block comment should start with '# '
urls.py:25:5: E265 block comment should start with '# '
urls.py:27:5: E265 block comment should start with '# '
views.py:28:1: E302 expected 2 blank lines, found 1
views.py:45:1: E302 expected 2 blank lines, found 1
views.py:67:1: E302 expected 2 blank lines, found 1
views.py:72:80: E501 line too long (81 > 79 characters)
views.py:83:1: E302 expected 2 blank lines, found 1
views.py:121:33: F821 undefined name 'form'
views.py:130:1: E303 too many blank lines (3)

Upload-File : Add response message to indicate upload success or failure

Currently a file is uploaded but there no message to the user whether the upload succeeded or failed. The user interface should communicate to the user that the file was uploaded and can be viewed by clicking on the Display-Files link. If the file failed to upload, that should be communicated to along with information about what action the user might take.

Parse the PARAMETER section

Refactor /upload messaging to use Djangos messaging framework

File Upload : display upload result

Update to Django 3.0.6 and DjangoRestFramework 3.11.0

Update README.md for v0.1.0

• remove : 'upload the file to las-util-flask/src/uploads'

Parse the CURVE section

Initial iteration toward responsive multiple device formats display

Make release package for v0.1.0

Make the changes to the project that enable making a release with metadata appropriate for GitHub and for Django projects.

Testing: Add tests for Well data parsed from a las file

ASCII (Data) Section: research ways to display the data

Research/review options for sensibly displaying the data section.

Some possibilities to explore at:

• Mathplotlib
• Plotly
• Wellio.js
• html/css

Fix layout display issue: Copyright floats on to display data.

Display-Files: Move 'Filename' from a column to be a header for all of the files content

Bug: ValueError on uploading sample_2.0.las

Exception Type: ValueError
Exception Value: not enough values to unpack (expected 2, got 1)
Exception Location:
/usr/local/devel/Apps/django-apps/workdir/las-util-django/src/las_util/cntrl.py in parse, line 54

Data section: '~Other'
Data line: ' Note: The logging tools became stuck at 625 metres causing the data'

ASCII (Data) Section : Implement beta level data display.

After researching data display methods in #26, choose one and implement at beta-level quality. The purpose of this ticket is to explore what challenges there might be with the selected display method.

ASCII (Data) Section : Alpha level parsing of the ~ASCII (data) section

• Parse a small regular-ish ~ASCII (data) section.
• Display the data in a rudimentary way on the Detail-Display.