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.

Sign up for GitHub

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

Jump to bottom

Avoid creating SparseVectors for LOCO #377

Merged
merged 19 commits into from
Aug 21, 2019
Merged

Avoid creating SparseVectors for LOCO #377

Changes from 1 commit
Commits
Show all changes
19 commits
Select commit Hold shift + click to select a range
66a5e99
WIP
gerashegalov Aug 3, 2019
77b97ee
code check fixes
gerashegalov Aug 5, 2019
35b8b5c
try sparse vector clone for test fix
gerashegalov Aug 5, 2019
cb2dc05
Merge branch 'master' into gera/perf-regression
michaelweilsalesforce Aug 7, 2019
a494129
WIP
gerashegalov Aug 3, 2019
1c383e5
code check fixes
gerashegalov Aug 5, 2019
a1d7d81
try sparse vector clone for test fix
gerashegalov Aug 5, 2019
f95f4bf
better names
gerashegalov Aug 8, 2019
a8ff84f
Skip Zeros when computing LOCOs for Text and Date fields
mweilsalesforce Aug 8, 2019
709594f
Merge branch 'gera/perf-regression' of github.com:gerashegalov/Transm…
mweilsalesforce Aug 8, 2019
96b2941
Fix Scalastyle
mweilsalesforce Aug 8, 2019
ee76053
minor fixes
gerashegalov Aug 8, 2019
2248d49
zipped
gerashegalov Aug 8, 2019
c3f743d
redundant toArray
gerashegalov Aug 8, 2019
dc39cb3
Updating comments + adding extra checks
mweilsalesforce Aug 9, 2019
25a6ac5
Merge branch 'master' into gera/perf-regression
leahmcguire Aug 12, 2019
3b7b63a
Adding TODO
mweilsalesforce Aug 12, 2019
b271b74
Merge branch 'master' into gera/perf-regression
tovbinm Aug 20, 2019
087b1d2
Merge branch 'master' into gera/perf-regression
leahmcguire Aug 21, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Adding TODO
  • Loading branch information
@mweilsalesforce
mweilsalesforce committed Aug 12, 2019
commit 3b7b63adaf1086d40f8ecc8cd8f583d2c79046be
2 changes: 2 additions & 0 deletions core/src/main/scala/com/salesforce/op/stages/impl/insights/RecordInsightsLOCO.scala
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -156,6 +156,8 @@ class RecordInsightsLOCO[T <: Model[T]]

// If the descriptor value of a derived feature exists, then we check if it is
// from unit circle transformer. We aggregate such features for each (rawFeatureName, timePeriod).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is true now - but may not always be true. If you want this to apply only for date unit circles should also check that one of the parentFeatureStages is a DateToUnitCircleTransformer or DateToUnitCircleVectorizer

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This check is not consistent : Unit Circle Transformation in DateMapVectorizer is not reflected in the parentStages (Seq[DateMapVectorizer] instead).
I think the check on descriptor value is coherent.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or I can check the parentType instead

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this change is explicitly to deal with date features that are transformed to unit circle then the check needs to be explicitly for that. Otherwise this is also applied to lat lon values (and anything else that we add later) and if we just check the type of the parent it assumes that we will always have unit circle transformation of dates - which could change at some point...

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree, but as I said above checking the parentFeatureStages won't work : for instance DateMapVectorizer may apply Unit circle transformation

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

DateMapVectorizer does days between reference date and the date. The only two that do unit vector are DateToUnitCircleTransformer and DateToUnitCircleVectorizer

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Then there must be a bug in the shortcut : when println(s"name ${history.columnName} stage ${history.parentFeatureStages} descriptor value ${history.descriptorValue}") I get

name dateMapFeature_k0_y_DayOfYear_33 stage ArrayBuffer(vecDateMap_DateMapVectorizer_00000000004c) descriptor value Some(y_DayOfYear)
name dateMapFeature_k1_x_DayOfYear_34 stage ArrayBuffer(vecDateMap_DateMapVectorizer_00000000004c) descriptor value Some(x_DayOfYear)
name dateMapFeature_k1_y_DayOfYear_35 stage ArrayBuffer(vecDateMap_DateMapVectorizer_00000000004c) descriptor value Some(y_DayOfYear)
name dateFeature_x_HourOfDay_0 stage ArrayBuffer() descriptor value Some(x_HourOfDay)
name dateFeature_y_HourOfDay_1 stage ArrayBuffer() descriptor value Some(y_HourOfDay)

Those features both use the .vetcorize shortcut.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

blarg! you are right there is a bug in the feature history that means we loose info if the same feature undergoes multiple transformations :-( https://github.com/salesforce/TransmogrifAI/blob/master/features/src/main/scala/com/salesforce/op/utils/spark/OpVectorMetadata.scala#L53

Can you put a todo to update once the bug is fixed

// TODO : Filter by parentStage (DateToUnitCircleTransformer & DateToUnitCircleVectorizer) once the bug in the
// feature history after multiple transformations has been fixed
name.map { n =>
val timePeriodName = if ((dateTypes ++ dateMapTypes).exists(history.parentFeatureType.contains)) {
history.descriptorValue
Expand Down