Overview AE Timelines AE Explorer Hep Explorer Delta-Delta Histogram Outlier Explorer Results Over Time

safety-results-over-time - Quality Control Details

This page provides a detailed report of the quality control documentation for safety-results-over-time. The source code for this page is available on github.

Technical Specs

Technical documentation including, functional specifications, regressions tests and risk assessments. see original

Functional Specifications

Filter by Measure

This drop-down menu is used to filter the lab variable that is displayed in the chart. The default measure is set to the first variable in the data set, but the default value can be adjusted to any measure upon the project team's request. Users can select any pre-defined measure in this filter. Selecting a measure will display the data points associated with that measure and will display the visits that the measure is collected at underneath the chart.

Filter by pre-selected characteristics

The chart can be configured to have any number of data filters. Each specified filter has a drop-down menu that is used to filter the visit data that is displayed in the chart.

Total Participants Shown

Displayed under the header, this statement provides the total number of participants in the data set in integers as well as the percentage of participants shown to one decimal place. In the default view, all participant data is included in the chart, or 100%, unless the project team requests otherwise. When filters are used, the data shown in the histogram is manipulated and the number of participant records shown at the top of the page may increase or decrease, depending on the variable selected.

Set Y-axis Limits

Users are able to adjust the lower limit of the y-axis by manipulating the input within the Lower Limit box. Users are able to adjust the upper limit of the y-axis by manipulating the input within the Upper Limit box. Each limit box has up and down arrows to adjust the value of the box by 1. Users can select an arrow to change the input or delete the current value in the box and type in a new value. When typing in a value, users must click outside of the box to apply the changes. When a user manipulates a y-axis limit, the y-axis on the chart below the controls will reflect the change.

Reset Y-axis limits

Users can change the upper and lower y-axis limits back to the default values for a measure by selecting the "Reset Limits" button. Pressing the button will erase the current values in the upper and lower limit boxes and replace them with defaults. The chart below will also reflect the changes and will show the default axes.

View Visits Without Data

Users can select the checkbox to view visits that do not contain data. Checking the box will show a timepoint for the visit. Unchecking the checkbox will hide the timepoint for visits without data; visits without data are hidden on default.

View Unscheduled Visits

Users can select the checkbox to view data that is not associated with a scheduled visit. Checking the box will show a timepoint for the unscheduled visit and its associated data. Unselecting the checkbox will hide the unscheduled visit timepoint and its data; unscheduled visits are hidden on default.

Box and Whisker Plots

The chart includes box and whisker plots to show the data distribution for a given measure. These plots show the data distribution for a data measure and can be added to the chart by clicking the box to the right of the Box plots text located above the chart. To take the plots away, the user can uncheck the box by clicking in it again. The box is checked by default, so the box and whisker plots appear when the chart is rendered.

Violin Plots

The chart includes violin plots to show the data distribution for a given measure. These plots show the data distribution for a data measure and can be added to the chart by clicking the box to the right of the Violin plots text located above the chart. To take the plots away, the user can uncheck the box by clicking in it again. The box is not checked by default, so the violin plots do not appear when the chart is rendered.

Regression Tests

Data Guidelines

Data Specifications for the charts. see original

The Safety Results Over Time accepts JSON data of the format returned by d3.csv(). The renderer visualizes clinical medical signs data with one row per participant per visit per medical sign plus the required variables specified below.

Data structure

one record per participant per visit per medical sign

Data specification

required and optional variables:

Setting Default Data Type Description Required?
id_col USUBJID character unique identifier of participant Yes
time_settings.value_col VISIT character visit name Yes
time_settings.order_col VISITNUM numeric visit order
measure_col TEST character measure name Yes
unit_col STRESU character measure unit
value_col STRESN numeric measure result Yes
normal_col_low STNRLO numeric LLN of measure
normal_col_high STNRHI numeric ULN of measure
filters[] either an array of filter variables and associated metadata
groups[] either an array of grouping variables and associated metadata

API

Technical specifications for API. see original

safetyResultsOverTime(element, settings)

a factory to create a custom Webcharts chart object

returns: chart

Param Type Description
element string CSS selector identifying the element in which to create the chart
settings object settings object specifying options for how the chart is to appear and behave. Options defined here overwrite default values; see Configuration

Chart Configuration

Technical specifications for chart configuration. see original

The most straightforward way to customize the Safety Results Over Time is by using a configuration object whose properties describe the behavior and appearance of the chart. Since the Safety Results Over Time is a Webcharts chart object, many default Webcharts settings are set in the defaultSettings.js file as described below. Refer to the Webcharts documentation for more details on these settings.

In addition to the standard Webcharts settings several custom settings not available in the base Webcharts library have been added to the Safety Results Over Time to facilitate data mapping and other custom functionality. These custom settings are described in detail below. All defaults can be overwritten by users.

Renderer-specific settings

The sections below describe each safety-results-over-time setting as of version 2.3.1.

settings.id_col

string

name of variable that captures unique identifier of participant

default: "USUBJID"

settings.time_settings

object

visit metadata

settings.timesettings.valuecol

string

name of variable that captures visit name

default: "VISIT"

settings.time_settings.label

string

Visit variable label

default: "Visit"

settings.timesettings.ordercol

string

name of variable that captures visit order

default: "VISITNUM"

settings.time_settings.order

array

Visit order

default: none

settings.timesettings.rotatetick_labels

boolean

Rotate tick labels 45 degrees?

default: true

settings.timesettings.verticalspace

number

Rotated tick label spacing

default: 100

settings.measure_col

string

name of variable that captures measure name

default: "TEST"

settings.unit_col

string

name of variable that captures measure unit

default: "STRESU"

settings.value_col

string

name of variable that captures measure result

default: "STRESN"

settings.normalcollow

string

name of variable that captures LLN of measure

default: "STNRLO"

settings.normalcolhigh

string

name of variable that captures ULN of measure

default: "STNRHI"

settings.start_value

string

value of measure to display initially

default: none

settings.filters

array

an array of filter variables and associated metadata

default: none

settings.filters[].value_col

string

Variable name

default: none

settings.filters[].label

string

Variable label

default: none

settings.groups

array

an array of grouping variables and associated metadata

default: none

settings.groups[].value_col

string

Variable name

default: none

settings.groups[].label

string

Variable label

default: none

settings.color_by

string

grouping variable; defaults to first item in groups setting; set to 'srot_none' to display chart without grouping on initialization

default: none

settings.boxplots

boolean

controls initial display of box plots

default: true

settings.outliers

boolean

controls initial display of outliers outside the 5th and 95th percentiles

default: true

settings.violins

boolean

controls initial display of violin plots

default: false

settings.missingValues

array

an array of strings that identify missing values in both the measure and result variables

default: none

settings.visitswithoutdata

boolean

controls display of visits without data for the current measure

default: false

settings.unscheduled_visits

boolean

controls display of unscheduled visits

default: false

settings.unscheduledvisitpattern

string

a regular expression that identifies unscheduled visits

default: "/unscheduled|early termination/i"

settings.unscheduledvisitvalues

array

an array of strings that identify unscheduled visits; overrides unscheduledvisitpattern

default: none

Webcharts settings

The object below contains Webcharts settings as of version 2.3.1 of the Safety Results Over Time.

{
    "x": {
        "column": null,
        "type": "ordinal",
        "label": null,
        "behavior": "flex",
        "sort": "alphabetical-ascending",
        "tickAttr": null
    },
    "y": {
        "column": null,
        "type": "linear",
        "label": null,
        "behavior": "flex",
        "stat": "mean",
        "format": null
    },
    "marks": [
        {
            "type": "line",
            "per": null,
            "attributes": {
                "stroke-width": 2,
                "stroke-opacity": 1,
                "display": "none"
            }
        },
        {
            "type": "circle",
            "per": null,
            "attributes": {
                "stroke": "black",
                "stroke-opacity": 0,
                "fill-opacity": 0
            },
            "values": {
                "srot_outlier": [
                    true
                ]
            },
            "radius": null,
            "tooltip": null,
            "hidden": true
        },
        {
            "type": "circle",
            "per": null,
            "attributes": {
                "stroke": "black",
                "stroke-opacity": 1,
                "fill-opacity": 1
            },
            "values": {
                "srot_outlier": [
                    true
                ]
            },
            "radius": 1.75,
            "tooltip": null,
            "hidden": false
        }
    ],
    "legend": {
        "mark": "square"
    },
    "color_by": null,
    "resizable": true,
    "gridlines": "y",
    "aspect": 3
}

Testing Logs

Interactive log of QC for all code updates. Includes code reviews, feature testing and regression testing for all releases. see original
PullRequestRequesterDateRequestedBranchTargetTitleReviewIDReviewerReviewDateReviewStatusMergedByDateMergedReviewComments
0004jwildfire2016-04-15T17:44:50Zadjust-ticksmasterNew functionality for tick rotation and violin plots. NONEjwildfire2016-04-15T17:44:57Z
0007jwildfire2016-05-25T20:04:26ZreorgmasterReorgNONENathan Bryant2016-06-08T14:39:06Z
0016jwildfire2016-12-17T16:28:29Zv1.3.0masterSafety Results Over Time v1.3.0NONEjwildfire2017-02-23T21:31:46Z
0018samussiah2017-01-25T22:20:49Zcustom-filtersv1.3.0Add custom filters, remove chart-foundry references, and refactor a bit.21902013jwildfire2017-02-15T00:52:52ZAPPROVEDSpencer Childress2017-02-16T19:04:45ZGoing to go ahead and approve this for merge, but will create a few issues based on my comments that we may want to address before release. ;;Should create issue to make unit and the normal ranges optional. ;;I wonder if the default here should just be "none" and the users can configure additional groups as desired ;;`e.NONE='All'` is like a metaphysical riddle or something. ;;We should bite the bullet and update the way we merge settings eventually, but not for this round of releases ... likely to bite us at some point though ...
0018samussiah2017-01-25T22:20:49Zcustom-filtersv1.3.0Add custom filters, remove chart-foundry references, and refactor a bit.21903361jwildfire2017-02-15T00:54:08ZCOMMENTEDSpencer Childress2017-02-16T19:04:45ZYou already have this covered in #19.
0018samussiah2017-01-25T22:20:49Zcustom-filtersv1.3.0Add custom filters, remove chart-foundry references, and refactor a bit.21903621jwildfire2017-02-15T00:56:08ZCOMMENTEDSpencer Childress2017-02-16T19:04:45ZCreated #23
0018samussiah2017-01-25T22:20:49Zcustom-filtersv1.3.0Add custom filters, remove chart-foundry references, and refactor a bit.21903972jwildfire2017-02-15T00:59:07ZCOMMENTEDSpencer Childress2017-02-16T19:04:45Zcreated an [issue](https://github.com/RhoInc/webcharts-wrapper-boilerplate/issues/4)
0018samussiah2017-01-25T22:20:49Zcustom-filtersv1.3.0Add custom filters, remove chart-foundry references, and refactor a bit.21904078jwildfire2017-02-15T00:59:56ZCOMMENTEDSpencer Childress2017-02-16T19:04:45ZThis is the only change we need for 2.0.0, I think.
0020samussiah2017-02-06T20:44:27Zrotate-tick-labelsv1.3.0Rotate tick labels & Improvements to box and violin plots21905012jwildfire2017-02-15T01:12:21ZAPPROVEDSpencer Childress2017-02-16T19:16:29ZApproved with 🎆. Very nice. ;;Good stuff. Much cleaner box/violin plot implementation. 👏👏👏;;Would definitely be good to share these improvements. At the very least we should put them in a new stand-alone example so that we don't forget about them. ;; ;; Still thinking it would be nice to implement a boxplot 'mark' in webcharts. Maybe a worthy Rho24?
0020samussiah2017-02-06T20:44:27Zrotate-tick-labelsv1.3.0Rotate tick labels & Improvements to box and violin plots21905901jwildfire2017-02-15T01:14:56ZCOMMENTEDSpencer Childress2017-02-16T19:16:29Zwebcharts specific now (instead of generic D3 function). Not a problem, just worth noting.
0020samussiah2017-02-06T20:44:27Zrotate-tick-labelsv1.3.0Rotate tick labels & Improvements to box and violin plots21906154jwildfire2017-02-15T01:17:11ZCOMMENTEDSpencer Childress2017-02-16T19:16:29Zhonestly, if we're going to take it this far. it might be better just to send it the chart object and nothing else. Just have `group`, `boxInsideColor` and `precision` as options for the user there.
0020samussiah2017-02-06T20:44:27Zrotate-tick-labelsv1.3.0Rotate tick labels & Improvements to box and violin plots21906292jwildfire2017-02-15T01:18:08ZCOMMENTEDSpencer Childress2017-02-16T19:16:29Zclever.
0020samussiah2017-02-06T20:44:27Zrotate-tick-labelsv1.3.0Rotate tick labels & Improvements to box and violin plots22335380samussiah2017-02-16T19:05:53ZCOMMENTEDSpencer Childress2017-02-16T19:16:29ZI like that idea a lot!
0020samussiah2017-02-06T20:44:27Zrotate-tick-labelsv1.3.0Rotate tick labels & Improvements to box and violin plots22337714samussiah2017-02-16T19:15:40ZCOMMENTEDSpencer Childress2017-02-16T19:16:29ZThe group object has a bunch of items of interest, most importantly:;; ;; * The x-axis value at which to plot the box plot;; * The group value with which to offset the the box plot;; * The nested group data;; ;; Rather than pass each of those to the function I thought it would be nicer to just wrap 'em up in a single object.
0020samussiah2017-02-06T20:44:27Zrotate-tick-labelsv1.3.0Rotate tick labels & Improvements to box and violin plots22337872samussiah2017-02-16T19:16:18ZCOMMENTEDSpencer Childress2017-02-16T19:16:29ZHacky ;-);; ;; I want my darn violin plots to touch the min and max!
0021samussiah2017-02-08T20:13:19Zannotate-populationv1.3.0Add population annotation.21907008jwildfire2017-02-15T01:24:11ZAPPROVEDSpencer Childress2017-02-16T19:19:36ZEasy peasy.
0022samussiah2017-02-09T19:37:02Zconsistent-axes-plus-log-linearv1.3.0Consistent axes plus log linear21907223jwildfire2017-02-15T03:21:17ZAPPROVEDSpencer Childress2017-02-16T19:53:50Zwhy bring `i` along for the ride here? ;;so nesting by visit and group;;Is the nested data used in the boxplots?
0022samussiah2017-02-09T19:37:02Zconsistent-axes-plus-log-linearv1.3.0Consistent axes plus log linear22339300samussiah2017-02-16T19:22:31ZCOMMENTEDSpencer Childress2017-02-16T19:53:50Zno idea, removed
0022samussiah2017-02-09T19:37:02Zconsistent-axes-plus-log-linearv1.3.0Consistent axes plus log linear22339641samussiah2017-02-16T19:23:55ZCOMMENTEDSpencer Childress2017-02-16T19:53:50ZYup!
0024samussiah2017-02-16T21:55:42Zgroups-defaultv1.3.0Update default grouping to none and hide group control when only one …22372748samussiah2017-02-16T21:56:39ZCOMMENTEDSpencer Childress2017-02-16T21:56:44ZLooks good to me.
0027jwildfire2017-03-07T02:28:04Zv2.0.1masterv2.0.1NONEjwildfire2017-03-13T23:31:26Z
0028samussiah2017-03-07T22:19:35Zlog-fixv2.0.1Fix logged axis bug.25840368jwildfire2017-03-08T18:19:23ZCHANGES_REQUESTEDSpencer ChildressI think I'd rather do this in the control instead of deleting all 0 values on pre-process.
0033jwildfire2017-10-12T23:09:56Zv2.0.2-devmasterV2.0.2 dev69263644samussiah2017-10-13T15:23:07ZAPPROVEDjwildfire2017-10-13T20:59:16Z
0035samussiah2017-10-20T13:58:34Zv2.0.3-devmasterV2.0.3 dev70860678jwildfire2017-10-20T14:31:08ZAPPROVEDjwildfire2017-10-20T14:31:24Z
0039mhickle2017-12-13T15:54:12ZReadMemasterRead me84246923brittsikora2017-12-18T19:42:02ZAPPROVEDmhickle2017-12-18T19:43:00Z
0040samussiah2018-01-05T14:59:25Zv2.1.0-devmasterv2.1.0-devNONEjwildfire2018-01-15T23:31:38Z
0042samussiah2018-01-05T18:26:12Zy-axis-limitsv2.1.0-devadd y-axis domain controls87103473jwildfire2018-01-07T16:16:08ZCHANGES_REQUESTEDjwildfire2018-01-11T17:04:35ZGenerally looks good, but found a few small issues in QC. ;; 1) Need a clippath applied or bars overlap axis once filtered. ;; 2) "None" now appears twice in the group dropdown.;; 3) Turning on violin plots not working as expected (only rendering for first visit)
0042samussiah2018-01-05T18:26:12Zy-axis-limitsv2.1.0-devadd y-axis domain controls88234332jwildfire2018-01-11T17:02:12ZAPPROVEDjwildfire2018-01-11T17:04:35Z👍 Looks great to me.
0044samussiah2018-01-15T23:46:04Zv2.2.0-devmasterSafety Results Over Time v2.2.093728962brittsikora2018-02-02T19:24:33ZAPPROVEDsamussiah2018-02-02T21:43:37ZPassing regression testing in firefox and chrome
0046samussiah2018-01-16T19:22:01Zvisitnum-orderv2.2.0-devVisit order89510084jwildfire2018-01-17T16:54:00ZCHANGES_REQUESTEDSpencer Childress2018-02-01T22:34:42ZCode generally looks good to me, but chart bombed when I tried these settings in CAT: `{"time_settings":{"order":["Visit 2","Visit 5"]}}`;; ;; I was expecting Visit 2 and Visit 5 to be pulled to the left on the x-axis ... ;;So the `order` option basically overwrites the `order_col` option. ;;so `x.order` will be null unless `time_settings.order` is defined. Should be ok ...
0046samussiah2018-01-16T19:22:01Zvisitnum-orderv2.2.0-devVisit order89674774jwildfire2018-01-18T05:17:00ZAPPROVEDSpencer Childress2018-02-01T22:34:42Z👍
0046samussiah2018-01-16T19:22:01Zvisitnum-orderv2.2.0-devVisit order93162159brittsikora2018-02-01T04:04:08ZAPPROVEDSpencer Childress2018-02-01T22:34:42Z
0047samussiah2018-01-18T00:01:04Zunscheduled-visitsv2.2.0-devUnscheduled visits89976822jwildfire2018-01-19T00:09:03ZCHANGES_REQUESTEDSpencer Childress2018-02-01T22:34:51ZHave we confirmed with Jack that this is ok to remove? Seems like it would be easy enough to keep. Maybe just refactor using the same workflow as `removeUnscheduledVisits.js` below. ;;On further thought, I think the "hide visits with no data" control is worth keeping unless there is a compelling reason not to do so ...
0047samussiah2018-01-18T00:01:04Zunscheduled-visitsv2.2.0-devUnscheduled visits89978985jwildfire2018-01-19T00:19:53ZCOMMENTEDSpencer Childress2018-02-01T22:34:51ZI would probably lean towards making this text based instead of requiring users to understand regex. Or I suppose we could support both by adding `unscheduled_visit_terms:["unscheduled","early termination"]` alongside the `unscheduled_visit_pattern` and then building some logic regarding which one takes precedence ...
0047samussiah2018-01-18T00:01:04Zunscheduled-visitsv2.2.0-devUnscheduled visits90264514samussiah2018-01-19T22:27:41ZCOMMENTEDSpencer Childress2018-02-01T22:34:51ZYeah, on second thought it's nice to have.
0047samussiah2018-01-18T00:01:04Zunscheduled-visitsv2.2.0-devUnscheduled visits90264981samussiah2018-01-19T22:30:06ZCOMMENTEDSpencer Childress2018-02-01T22:34:51ZThe problem is unscheduled visits typically have a suffix that indicates where the visit fell in the schedule of events. I've added another parameter, `unscheduled_visit_values` that default to `null` but overrides the `unscheduled_visit_pattern` if specified.
0047samussiah2018-01-18T00:01:04Zunscheduled-visitsv2.2.0-devUnscheduled visits90708577jwildfire2018-01-23T05:04:35ZAPPROVEDSpencer Childress2018-02-01T22:34:51ZLooks good.;;I think I'd vote for `unscheduled visits` to be `true` by default. ;;nevermind - I'd didn't notice the control. I think it's looking good as is.
0047samussiah2018-01-18T00:01:04Zunscheduled-visitsv2.2.0-devUnscheduled visits93164310brittsikora2018-02-01T04:25:39ZAPPROVEDSpencer Childress2018-02-01T22:34:51Z
0048samussiah2018-01-18T21:27:40Zsettings-schemav2.2.0-devSettings schema89977768jwildfire2018-01-19T00:25:30ZCHANGES_REQUESTEDSpencer Childress2018-02-01T22:35:00ZMinor tweaks likely needed after changes to #47. ;;👍 good catch;;default = false, no? ;;is this a string? or a regular expression? (maybe json schema only supports strings?);;update based on comments from #47 ;;nevermind - i see the logic below dealing with this. ;;This looks good - should also make it easier to support `config.unscheduled_visit_list` as suggested in #47 code review
0048samussiah2018-01-18T21:27:40Zsettings-schemav2.2.0-devSettings schema92092688jwildfire2018-01-29T05:11:06ZAPPROVEDSpencer Childress2018-02-01T22:35:00ZNot sure I totally see the point of splitting the settings here, but I guess it doesn't hurt anything ... so 🤷‍♂️ ;;As mentioned elsewhere, we should move this to a footnote. Created #50
0048samussiah2018-01-18T21:27:40Zsettings-schemav2.2.0-devSettings schema92237489samussiah2018-01-29T15:19:28ZCOMMENTEDSpencer Childress2018-02-01T22:35:00ZI needed to pull in the webcharts settings for the [configuration wiki](https://github.com/RhoInc/safety-results-over-time/wiki/Configuration) and this was the hacky route I chose.
0048samussiah2018-01-18T21:27:40Zsettings-schemav2.2.0-devSettings schema93165133brittsikora2018-02-01T04:33:47ZAPPROVEDSpencer Childress2018-02-01T22:35:00ZFeature testing passes
0051samussiah2018-02-27T14:56:32Zv2.2.1-devmasterSafety Results Over Time - v2.2.1100106134pburnsdata2018-02-28T15:27:42ZAPPROVEDsamussiah2018-03-09T20:22:14Z
0051samussiah2018-02-27T14:56:32Zv2.2.1-devmasterSafety Results Over Time - v2.2.1102770035dschwentker2018-03-09T19:55:54ZAPPROVEDsamussiah2018-03-09T20:22:14ZTested and passed using webcharts version v1.10.0-dev. Confirmed that there are 0 results when running d3.selectAll('.wc-controls .control-label') in the console.
0055samussiah2018-04-02T14:19:20Zv2.2.2-devmasterSafety Results Over Time v2.2.2116959651emmorris2018-05-02T15:56:51ZAPPROVEDSpencer Childress2018-05-02T20:41:12Z
0056samussiah2018-04-02T17:49:34Zadd-test-pagev2.2.2-devadd test page109001458pburnsdata2018-04-03T15:35:38ZAPPROVEDSpencer Childress2018-04-30T19:52:26Z
0059brittsikora2018-05-01T19:58:07Zbrittsikora-patch-1masterUpdating example link116683861samussiah2018-05-01T20:04:17ZAPPROVEDSpencer Childress2018-05-01T20:04:23Zmagnificent!
0063rtbailey2018-08-09T19:47:07Zrtbailey-patch-1masterUpdate LICENSE.md167596899samussiah2018-10-23T19:28:34ZAPPROVEDRyan Bailey
0064samussiah2018-10-23T19:27:59Zv2.2.3-devmasterSafety Results Over Time v2.2.3167731168jwildfire2018-10-24T05:07:31ZAPPROVEDjwildfire2018-10-25T15:46:46Z👍
0066samussiah2018-12-18T17:06:26Zdev-v2.3.0masterSafety Results Over Time v2.3.0198170571dschwentker2019-01-30T16:19:57ZAPPROVEDSpencer Childress2019-01-30T16:59:08ZRegression testing passed in Firefox and Chrome.
0068samussiah2019-01-02T19:14:30Zlegend-orderdev-v2.3.0Sync order of box and violin plots with legend order.190745838pburnsdata2019-01-09T14:21:27ZAPPROVEDSpencer Childress2019-01-29T21:33:07ZMuch improved- nice work;;interesante;;This is neat - cool to see individual subgroups show up far left etc.
0068samussiah2019-01-02T19:14:30Zlegend-orderdev-v2.3.0Sync order of box and violin plots with legend order.197790149dschwentker2019-01-29T21:21:44ZAPPROVEDSpencer Childress2019-01-29T21:33:07ZTested and passed
0069samussiah2019-01-02T19:14:52Ztooltip-precisiondev-v2.3.0Improve precision in tooltips.190748815pburnsdata2019-01-09T14:28:35ZAPPROVEDSpencer Childress2019-01-29T21:33:15ZVery precise, very precise;;good call moving precision in here;;here we go
0069samussiah2019-01-02T19:14:52Ztooltip-precisiondev-v2.3.0Improve precision in tooltips.197790677dschwentker2019-01-29T21:22:56ZAPPROVEDSpencer Childress2019-01-29T21:33:15ZTested and approved
0070samussiah2019-01-02T19:15:15Zoutliersdev-v2.3.0Draw outliers.190753858pburnsdata2019-01-09T14:43:07ZAPPROVEDSpencer Childress2019-01-29T21:33:24Z@samussiah Looks good! My only thought would be that since the outliers are colored so similarly, they're difficult to see with the violin plot, but I suppose you are really looking at the full density when you're using the violin plot so they're part of the violin plot anyway. I'm thinking you really only care about seeing the outliers when you use boxplot so it doesn't really matter if the violin plot covers them up some? ;;do you want to remove this?;;cool - I've never used Map() and it looks super useful. Love that it's an iterable.
0070samussiah2019-01-02T19:15:15Zoutliersdev-v2.3.0Draw outliers.197790971dschwentker2019-01-29T21:23:40ZAPPROVEDSpencer Childress2019-01-29T21:33:24ZTested and approved
0071samussiah2019-01-02T19:15:36Zlog-axisdev-v2.3.0Add log axis functionality.191784792pburnsdata2019-01-11T18:21:37ZCOMMENTEDSpencer Childress2019-01-29T21:33:40Zget that outta here
0071samussiah2019-01-02T19:15:36Zlog-axisdev-v2.3.0Add log axis functionality.191785563pburnsdata2019-01-11T18:23:48ZCOMMENTEDSpencer Childress2019-01-29T21:33:40Zsolid usage of small - much respect
0071samussiah2019-01-02T19:15:36Zlog-axisdev-v2.3.0Add log axis functionality.191791014pburnsdata2019-01-11T18:38:34ZCOMMENTEDSpencer Childress2019-01-29T21:33:40ZI'm wondering if the log ticks should be treated differently? @samussiah - they might get lil squished
0071samussiah2019-01-02T19:15:36Zlog-axisdev-v2.3.0Add log axis functionality.191791776pburnsdata2019-01-11T18:40:36ZCOMMENTEDSpencer Childress2019-01-29T21:33:40Zcool
0071samussiah2019-01-02T19:15:36Zlog-axisdev-v2.3.0Add log axis functionality.191794571samussiah2019-01-11T18:48:17ZCOMMENTEDSpencer Childress2019-01-29T21:33:40ZWhat's a log equivalent of quantiles?
0071samussiah2019-01-02T19:15:36Zlog-axisdev-v2.3.0Add log axis functionality.192361255pburnsdata2019-01-14T21:02:57ZCOMMENTEDSpencer Childress2019-01-29T21:33:40Z@samussiah started looking at the log quantile stuff and saw this - should be removeYAxisTicks()
0071samussiah2019-01-02T19:15:36Zlog-axisdev-v2.3.0Add log axis functionality.192733351pburnsdata2019-01-15T16:19:11ZCOMMENTEDSpencer Childress2019-01-29T21:33:40ZCreated #76 for this
0071samussiah2019-01-02T19:15:36Zlog-axisdev-v2.3.0Add log axis functionality.192733887pburnsdata2019-01-15T16:20:06ZAPPROVEDSpencer Childress2019-01-29T21:33:40ZApproved - Spencer to fix add/remove tick issues in later pr
0071samussiah2019-01-02T19:15:36Zlog-axisdev-v2.3.0Add log axis functionality.197788812dschwentker2019-01-29T21:18:33ZAPPROVEDSpencer Childress2019-01-29T21:33:40ZTested and passed
0072samussiah2019-01-02T19:15:57Zgroup-labelsdev-v2.3.0Display group labels in group dropdown.191795979pburnsdata2019-01-11T18:51:59ZCOMMENTEDSpencer Childress2019-01-29T21:33:47Zwhats srot? just curious
0072samussiah2019-01-02T19:15:57Zgroup-labelsdev-v2.3.0Display group labels in group dropdown.191800184pburnsdata2019-01-11T19:02:37ZAPPROVEDSpencer Childress2019-01-29T21:33:47Z
0072samussiah2019-01-02T19:15:57Zgroup-labelsdev-v2.3.0Display group labels in group dropdown.197791096dschwentker2019-01-29T21:23:57ZAPPROVEDSpencer Childress2019-01-29T21:33:47ZTested and approved
0073samussiah2019-01-02T19:21:18Zoptionalize-variablesdev-v2.3.0Optionalize the unit_col setting.191801456pburnsdata2019-01-11T19:05:59ZAPPROVEDsamussiah2019-01-29T21:33:48Zunits4days
0074pburnsdata2019-01-08T21:17:01Zpburnsdata-patch-1dev-v2.3.0Resolve spelling error in readme194152949samussiah2019-01-18T15:38:21ZAPPROVEDSpencer Childress2019-01-18T15:38:31Z
0078samussiah2019-01-18T15:35:12Zmiscellanydev-v2.3.0Miscellany194296527pburnsdata2019-01-18T22:07:13ZCOMMENTEDSpencer Childress2019-01-29T21:39:02Zthis is super cool;;looks much better but some weird stuff happening. I'm seeing that Direct Bilirubin has an 000004 guy, or ALT has repeated 0.0s, and temperature doesnt have an axis @samussiah I was playing with it some too -> could be worth changing the format - im just not sure why the 0.0s and no axis ones are happening
0078samussiah2019-01-18T15:35:12Zmiscellanydev-v2.3.0Miscellany195070218pburnsdata2019-01-22T15:36:59ZAPPROVEDSpencer Childress2019-01-29T21:39:02ZNice work as always. Looks good to me!;;this looks nice;;the power of regex;;lookin better to me!
0078samussiah2019-01-18T15:35:12Zmiscellanydev-v2.3.0Miscellany197791217dschwentker2019-01-29T21:24:14ZAPPROVEDSpencer Childress2019-01-29T21:39:02ZTested and approved
0081samussiah2019-01-29T16:47:21Zbug-fixesdev-v2.3.0Bug fixes197712381pburnsdata2019-01-29T18:28:27ZAPPROVEDSpencer Childress2019-01-29T21:39:11ZLooks swell
0081samussiah2019-01-29T16:47:21Zbug-fixesdev-v2.3.0Bug fixes197788445dschwentker2019-01-29T21:17:43ZAPPROVEDSpencer Childress2019-01-29T21:39:11ZTested and passed
0085samussiah2019-02-07T16:31:29Zdev-v2.3.1masterSafety Results over Time v2.3.1207420929pburnsdata2019-02-25T14:30:19ZAPPROVEDPreston Burns2019-03-06T21:29:34ZThat's a wrap!;;This I promise you
0085samussiah2019-02-07T16:31:29Zdev-v2.3.1masterSafety Results over Time v2.3.1211480755dschwentker2019-03-06T21:22:10ZAPPROVEDPreston Burns2019-03-06T21:29:34ZTested and confirmed #84. Other two issues require no testing. Passed and approved.
0087samussiah2019-03-11T22:16:07Zadd-color_by-to-schemamasterAdd color_by to settings-schema.jsonNONESpencer Childress2019-04-01T17:51:45Z
0088samussiah2019-03-27T20:22:33Zdev-v2.3.2masterdev-v2.3.2220027598jwildfire2019-03-28T13:45:48ZAPPROVEDSpencer Childress2019-04-01T17:51:44ZIs this really numeric?
0088samussiah2019-03-27T20:22:33Zdev-v2.3.2masterdev-v2.3.2220029500samussiah2019-03-28T13:48:46ZCOMMENTEDSpencer Childress2019-04-01T17:51:44Zheh nope
0091jwildfire2019-05-16T03:35:31Zdev-v2.3.3masterDev v2.3.3238435430pburnsdata2019-05-16T14:35:33ZAPPROVEDPreston Burns2019-05-16T15:03:59ZLookin good
0093dependabot[bot]2019-07-12T04:22:54Zdependabot/npm_and_yarn/lodash-4.17.14masterBump lodash from 4.17.11 to 4.17.14261296294samussiah2019-07-12T14:36:45ZAPPROVEDSpencer Childress2019-07-12T14:37:14Z