Requesting multiple metrics sometimes give different results to requesting them individually

Description of Bug

Sometimes, when a single metric is requested with get_metric_values, it returns a value for a particular time. But if both that metric and another are requested simultaneously, even if they both have a value at the same time, the value returned for the first metric is None.

Steps To Reproduce

Run this, noting that the run is on trial3. then comment out line 7, uncomment line 8, and run it again:

import simvue

run_id = "AZPKJLrtwr3ZerLi4QNnu8"

client = simvue.Client()

metric_names = ["soot_visibility.z.7_0.avg", "soot_visibility.z.37_0.avg"]
#metric_names = ["soot_visibility.z.7_0.avg"]

all_metric_values = client.get_metric_values(metric_names, 'time', run_ids=[run_id])

for (metric_name, single_metric_values) in all_metric_values.items():
    print(f"{metric_name}: {list(single_metric_values.items())[-1]}")

Output:

soot_visibility.z.37_0.avg: ((1731.6583251953125, 'AZPKJLrtwr3ZerLi4QNnu8'), 29.584584259066062)
soot_visibility.z.7_0.avg: ((1731.6583251953125, 'AZPKJLrtwr3ZerLi4QNnu8'), None)

Output with line 8 instead of 7:

soot_visibility.z.7_0.avg: ((1731.6583251953125, 'AZPKJLrtwr3ZerLi4QNnu8'), 19.169060055914873)

Setup

• OS: Ubuntu
• python-api version v2.3.5

Commencez par l’appel à get_metric_values et exécutez la reproduction fournie avec trial3 en utilisant les deux configurations de metric_names. Comparez les valeurs renvoyées pour l’horodatage commun ; c’est terminé lorsque la demande de plusieurs métriques conserve la même valeur que celle renvoyée lorsque la métrique concernée est demandée individuellement.