Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Telco_5G_QOE_Analysis_SQL Improvements #578

Open
DougEbel opened this issue Apr 3, 2024 · 0 comments
Open

Telco_5G_QOE_Analysis_SQL Improvements #578

DougEbel opened this issue Apr 3, 2024 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@DougEbel
Copy link
Collaborator

DougEbel commented Apr 3, 2024

I was using this to validate execution in Lake. As a byproduct, I identified markdown changes that would make it clearer:

  1. In 4.1 (and later steps), there are multiple comments/table names indicating that a graph is being produced, but no graph is produced until the step "select * from barGraph". We should say how we are accumulating data and add a comment to the select "Finally, display the barGraph.
  2. The comment Click on the cell in the IMAGE column to select it, then right click on the cell and select View Image. ... should add that they can use shift-mouse roll to increase the size of the graph (so they can read it)
  3. I'd repeat (parenthetically) the meaning of CQI and RSRP to help the user ... hold it ... We didn't define those metric anywhere
  4. No interpretation of the "Number of Ids in each QoE cluster" chart
  5. For Data preparation, the comment is "Before we can use the data in models we will perform some data preparation steps." ... What models and what do the models help us do to identify improvement opportunities
  6. For "Number of Ids in each QoE Cluster" graph, no conclusions of what the graph shows.
  7. No conclusions to "Number of Ids in each QoE Cluster in Test data by Decision Forest Model" ... what is the business impact? ... same for the XGB graph
  8. was running demo on Lake using PC Docker, but ran the requirements.txt used to provision CSAE environments. Got error that seems familiar:
    Unable to run SQL: Unable to run SQL query: Database reported error:7810:Error in function TD_GLM: Invalid input alias encountered. Please refer user guide.
    on:
    CREATE VOLATILE TABLE TD_Glm_FeatureSelection AS(
    SELECT * FROM TD_GLM (
    ON CLM_ADS_TRANSFORMED
    USING
@DougEbel DougEbel added the documentation Improvements or additions to documentation label Apr 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant