Development

[nathangeology]

Description

• Started adding new proposed abstractions for the templates in wellioviz, these are WIP and do not affect the current version's functionality. These will need ongoing discussion and improvement in future versions before replacing the current core functions.
• Updated with a new example of deploying wellioviz in Panel on a bokeh server.
• Updated the docs with instructions for running the panel example
• Added jest as a dev dependancy to the package and set up unit tests for the new template abstractions.

Related Issue

https://github.com/JustinGOSSES/wellioviz/issues/99 https://github.com/JustinGOSSES/wellioviz/issues/30 https://github.com/JustinGOSSES/wellioviz/issues/11 https://github.com/JustinGOSSES/wellioviz/issues/22

Motivation and Context

This was done as a part of the Transform 2020 hackathon and the goal is to keep pushing this towards being a powerful, professional, and open source well log visualization option for both python and javascript web application and notebook deployments.

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• [x] My code follows the code style of this project. ^^ ** The WIP code stills needs work to align the style as well as architecture discussion and alignment, but it is not the primary motivation for this pull request. These could be edited out by Justin prior to the merge if that is preferred and I can re-submit those changes when they are ready to roll out.
• [x] My change requires a change to the documentation.
• [x] I have updated the documentation accordingly.
• [x] I have added tests to cover my changes.
• [x] All new and existing tests passed.

[JustinGOSSES]

Wow, lots of good stuff in here. I've only looked at diff files so far. Will try to clone locally and run some checks Sunday or Monday, then merge into the master branch.

Can you talk a bit on how you envision people adding/sharing/changing things related to the log_curve_templates? I was thinking of doing at some of the styles via JSONs to make it easier to save, edit, and share styles. Is that something you could merge into your JS function based approach?

[JustinGOSSES]

Okay, had more time to look at the files. We're actually already aligned and I didn't realize earlier.