BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
FalkoSchulz
SAS Employee

No, It's just the sequence of events. The time/sequence is just required to keep events (within a transaction) in order.

Oscarboots
Quartz | Level 8

I won't bother you too much more Falko,

In the attached diagram from earlier in the thread, I'm not following why the graph does the following.

Apologies for repeating myself;

In the below diagram, what's causing the Green 'Ordered' & the Red 'Ordered' paths to merge when they have different Sequence dates?

Also I notice that the Blue 'Existing' & the Green 'Existing' have merged but they have different sequence dates too?

I think I could follow these diagrams better if I understood this behaviour.

The order of the Red path Events has also changed from the table compared to the diagram 'New' >> 'Ordered' >> 'Complained' has become 'New' >> 'Complained' >> 'Ordered' in the diagram. - I assume the diagram can make changes of the events if the dates are the same for that Trans_ID?

Thanks Falco, can you assist here?

Peter

  

TABLE.gif

sankey_1.gif

FalkoSchulz
SAS Employee

In regards to your questions:

In the below diagram, what's causing the Green 'Ordered' & the Red 'Ordered' paths to merge when they have different Sequence dates?

[Falko] These are merged because both 'Ordered' events are the 3rd event in each sequence of events (or 3rd step in a path). Well, now you may say - but 'Ordered' is not the 3rd in the red path. Problem here is the duplicate sequence value and related problem of path analysis not able to determine which comes first. See my answer for your last question below.

Also I notice that the Blue 'Existing' & the Green 'Existing' have merged but they have different sequence dates too?

[Falko] Same as before both 'Existing' events are the 4th step in each path and hence merged. Also same problem as before - your blue path has a duplicate sequence value for 'Existing' and 'Cancelled' and as such may appear in a wrong order.

The order of the Red path Events has also changed from the table compared to the diagram 'New' >> 'Ordered' >> 'Complained' has become 'New' >> 'Complained' >> 'Ordered' in the diagram. - I assume the diagram can make changes of the events if the dates are the same for that Trans_ID?

[Falko] Does the diagram show you a warning about 'artificial sequence orders' at the bottom? I would suspect so - since you have duplicate sequence dates within a single transaction. That means the path analysis algorithm can't determine which event occurred before the other potentially resulting in unexpected paths generated. This would also explain why you see the wrong order of 'Ordered->Complained' vs 'Complained->Ordered'.

Cheers, Falko

Oscarboots
Quartz | Level 8

Thanks Falco!!

Those points were throwing me off the track, I thought there was something about the number of the event having something to do with merging.

Now I understand the rules better, thanks again.

Oscarboots
Quartz | Level 8

Hi Falko,

I thought I'd show my progress since your advice has helped greatly.

I have the numbers by the Weight but the smaller weights don't display.

How would someone send this off for people to look at & interact with considering it's an Exploration rather than a report?

I'd like to send this off for people to select/deselect Events & see the impact, is this possible or is there a better way?

Thanks Peter.

sankeydiagram.gif 

Sample data

table1.gif

FalkoSchulz
SAS Employee

Glad you made progress! Looking good!

Yes, the diagram automatically adjust visible node values based on the space available. Since thinner paths don't provide enough room to display a value - the graph hides these. I'm not aware to have this behaviour changed at this stage. You can however see values by hovering over to see the tooltip or by looking at the detail table view (top right corner has a button for this). The detail table also has a nice behaviour to have the row selected of the current selected path.

Yes, since path analysis is only available within Explorer any consumers would need to open the exploration. The easiest way to share the information would be to send out a link to your exploration (you can use the File-Email option which generates the link for you).

Hope this helps. Regards, Falko

sas-innovate-2024.png

Don't miss out on SAS Innovate - Register now for the FREE Livestream!

Can't make it to Vegas? No problem! Watch our general sessions LIVE or on-demand starting April 17th. Hear from SAS execs, best-selling author Adam Grant, Hot Ones host Sean Evans, top tech journalist Kara Swisher, AI expert Cassie Kozyrkov, and the mind-blowing dance crew iLuminate! Plus, get access to over 20 breakout sessions.

 

Register now!

Tips for filtering data sources in SAS Visual Analytics

See how to use one filter for multiple data sources by mapping your data from SAS’ Alexandria McCall.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 20 replies
  • 6650 views
  • 9 likes
  • 4 in conversation