No, ruptures is a list of hazardlib objects wheres rupture_ids is a list of integers corresponding to the ids of the ruptures when stored on the db. I agree that this is not pretty, it is similar to the situation we have with the sites, with a dicotomy between hazardlib objects and database objects.

No problems in renaming compute_gmf_cache.