Update picam readme with notes about setting up aws lambda function (or workaround)

[sgbaird]

@Neil-YL do you know where this discussion is? I was pretty sure it was in one of the issues somewhere.. https://github.com/AccelerationConsortium/ac-training-lab/issues?q=is%3Aissue%20state%3Aopen%20aws

[sgbaird]

Also, seems that the title has some constraints:

Response: Error during 'create' for device '[undecided]-[undecided]-[undecided]': <HttpError 400 when requesting https://youtube.googleapis.com/youtube/v3/liveBroadcasts?part=snippet%2CcontentDetails%2Cstatus&alt=json returned "Title is invalid". Details: "[{'message': 'Title is invalid', 'domain': 'youtube.liveBroadcast', 'reason': 'invalidTitle', 'extendedHelp': 'https://developers.google.com/youtube/v3/live/docs/liveBroadcasts#snippet.title'}]">

The video's title. The property value has a maximum length of 100 characters and may contain all valid UTF-8 characters except < and >. You must set a value for this property if you call the videos.update method and are updating the snippet part of a video resource.

source: https://developers.google.com/youtube/v3/docs/videos#snippet.title

[sgbaird]

cc @Neil-YL, we might want to adjust the appended text to be a bit more concise, maybe @AC instead of @ Acceleration Consortium, stream instead of livestream.

I'm on the fence though

[Neil-YL]

I followed this one for the lambda setup: https://github.com/ACC-HelloWorld/5-data-logging#aws-lambda-function
I have not documented it further for the picam stream though. I think only thing worth mentioning other than the course5 instruction is the S3 token.pickle?

[Neil-YL]

cc @Neil-YL, we might want to adjust the appended text to be a bit more concise, maybe @AC instead of @ Acceleration Consortium, stream instead of livestream.

I'm on the fence though

Updated
broadcast_title = f"{workflow_name} stream @AC {cam_name}, {formatted_time}"

[sgbaird]

I followed this one for the lambda setup: https://github.com/ACC-HelloWorld/5-data-logging#aws-lambda-function
I have not documented it further for the picam stream though. I think only thing worth mentioning other than the course5 instruction is the S3 token.pickle?

Yes, I think just S3 token.pickle documentation which is in one of the issues and the new lambda function code that will be used instead (I guess by linking to a new colab notebook that generates the zip file?)

[Neil-YL]

I followed this one for the lambda setup: https://github.com/ACC-HelloWorld/5-data-logging#aws-lambda-function
I have not documented it further for the picam stream though. I think only thing worth mentioning other than the course5 instruction is the S3 token.pickle?

Yes, I think just S3 token.pickle documentation which is in one of the issues and the new lambda function code that will be used instead (I guess by linking to a new colab notebook that generates the zip file?)

This is the colab: https://colab.research.google.com/drive/1ApwqbTkNmUfOAlsTlrTavd4yR_tprOPT
I think once I finish the Chalice thing we may not need the colab zip file again.

[sgbaird]

Good point! I think we can probably keep the Colab for others to reproduce without requiring them to set up Chalice (i.e., have Chalice be optional), even though I realize that causes a version split.. open to thoughts.

For the Colab, I got the following when opening it:

Notebook loading error
There was an error loading this notebook. Ensure that the file is accessible and try again.
Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.

I found a trick for creating a Colab share link on mobile by changing the page settings to "desktop mode" in chrome (ignore if that's completely irrelevant 😅)

[sgbaird]

I guess that ?authuser=4 in the URL was the issue. https://colab.research.google.com/drive/1ApwqbTkNmUfOAlsTlrTavd4yR_tprOPT works fine for me (I went ahead and edited the URL above too)

[Neil-YL]

Good point! I think we can probably keep the Colab for others to reproduce without requiring them to set up Chalice (i.e., have Chalice be optional), even though I realize that causes a version split.. open to thoughts.

For the Colab, I got the following when opening it:

Notebook loading error
There was an error loading this notebook. Ensure that the file is accessible and try again.
Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.

I found a trick for creating a Colab share link on mobile by changing the page settings to "desktop mode" in chrome (ignore if that's completely irrelevant 😅)

I guess that ?authuser=4 in the URL was the issue. https://colab.research.google.com/drive/1ApwqbTkNmUfOAlsTlrTavd4yR_tprOPT works fine for me (I went ahead and edited the URL above too)

Thanks! I thought I shared it with my personal Google account (to make sure others can view it but not the editor permit)