wt1 | A simple , open and powerful Web tracker | Stream Processing library

One option to achieve your desired result:

1. Set clip="off" in coord_cartesian`
2. Make some room for the labels by increasing the bottom margin of the title
3. Set y=1.05 for the labels (the max of data range + the default expansion of the scale by .05)
4. Set min.segment.length=0
5. Increase the ylim for the labels
6. Nudge the position of the labels

Note: Getting your desired result you probably have to fiddle around with the values for the nudging, the ylim and the margin.

Your code is a mix of version 2, 4 and 5. Try upgrading all to v5.

This should work:

is your API gateway set up as a Proxy Lambda Integration or a Lambda Integration? Each has a different looking Event structure which changes where the keys are located.

Log the event ( print(event) will work just fine for a test run) then hit your endpoint and see what the event structure looks like. That will tell you where you keys are supposed to be or if you have the wrong key value (Event structures dont get updated often but it does happen, and tutorial videos become out of date pretty quick)

The Event for a Lambda is (and indeed, all events in all of AWS) are just JSON objects. using python, that directly translates to a Dictionary so having the right key structure can be a little weird to figure out because documentation on what various Events look like in the AWS Sphere are scattered througout the documentation and hard to find.

I usually keep a lambda on my console that all it does is print(event) then hook it up to whatever trigger I am trying to use at the time so i can see what it looks like nice and clear.

One more:

Funny that I've managed to find an answer by myself literally minutes after posting this, but I spent about 3 hours before trying to find and figure out a solution so I'll post my solution here instead of deleting the question, just in case someone else finds it helpful.

The solution I found was to reference the plot itself. So the plot name for the wt1 values is "WT Wave 1". Can reference the plot in the alert message like so:

Your data is duplicated because you are CONCATing the list of wt2.Names with the wt1.Name - ,wt1.Name). The one with NULL date isn't finding a matching record and is only showing the wt1.Name

Actually I think you may want to use the STUFF function instead of CONCAT to remove any extra slashes at the end.

looks like you want join normally and do left_join

It isn't working because you're using the input lengths in the cross() comparisons and not the EMAs themselves. So cross(EMA8, EMA21) is the equivalent of cross(8, 21). 8 and 21 are never going to cross, so never meet your condition. You need to assign a variable to each EMA and compare the actual EMAs instead eg

You can apply t.test rowwise and extract the p.value.