Ellie | ELLIE TEMPLATE FOR GHOST Get Ghost | Theme library

You'll want to convert those zone strings into actual Time.Zones, which can be done with justinmimbs' TimeZone library.

Then, you'll need to get the current time with something like Time.every, and convert it to local parts with Time.Extra.posixToParts.

Some example code:

Try adding the following line, this will fix it

The code below makes the following changes:

• renaming the variable dictionary to depth_to_site_dict
• in color_dict = {label: handles.get_color() ...}: changing handles to handle and get_color to get_facecolor() (the linked plot used a line plot, in this code we have a scatter plot)
• in handle.set_color(color_dict[dictionary[handle]]): use color_dict[depth_to_site_dict[label]]

IIUC, you can get all the rows with NaN and fill them with ['empty'] which you can then pass through the eval function:

With your current implementation it's not possible to know which apple to update since there's no unique attribute about the apples. What if two apples have the same size? If would be better if apples had IDs, or you used a dictionary type to keep track of the apples.

However, for the sake of demonstration, you could say that the list indeces of the apples are unique and you find them accordingly. In real life this will be a fragile solution.

Here's a naive approach using some helper functions from List.Extra.

Your loop can be made really simple. It has a couple of issues such as the one you mentioned, and another is dealing with multiple photographers and not just the first (Not sure if this is your actual use case):

Your code change: Remove your inner for loop as that's what duplicates everything:

you can do like this

If you didn't have any condition on employee ID at all you'd end up with records where a self-match had occurred, e.g. the results would show "Gracie Gardner was hired on the same day as Gracie Gardner"

We could then put ON e1.employee_id <> e2.employee_id - this would prevent Gracie matching with Gracie, but you'd then find "Gracie Gardner was hired on the same day as Summer Payne" and "Summer Payne was hired on the same day as Gracie Gardner" - i.e. you'd get "duplicate records" in terms of "person paired with person", each name being mentioned both ways round

Using greater than prevents this, and effectively means that any given pair of names only appears once. Because Gracie's ID is less than Summer's, you'll get Gracie in e1 paired with Summer in e2 but you won't get Summer in e1 paired with Gracie in e2

Another way of visualizing it is with a square/matrix

Adding height fill to each cell's attributes fixes your Ellie example: