Skip to main content

Coretype Collections Now Show Which Hardware Actually Ran

When a job runs on a Coretype Collection, the platform now displays which specific coretype was actually used.

What's New​

Collections group compatible coretypes so the platform can allocate the best available hardware while holding your price fixed. You always select and are billed for the Collection, but until now, you could not see which specific member coretype actually ran. That detail is now visible:

  • Jobs list Hardware column: Shows Collection (Actual Coretype) for completed jobs, for example "Emerald Plus (Emerald Max)"
  • Hardware Settings page: The Collection tile displays "Ran on: Emerald Max" (or whichever coretype ran) beneath the Collection name
  • Setup > Review page: After completion, shows Collection → Actual Coretype
  • Job CSV export: Two columns distinguish what you selected (hardware_setting) from what ran (coretype_name)

Why It Matters​

The actual coretype matters for performance analysis. If you are comparing runtime across jobs or debugging a solver's behavior, knowing whether the job ran on the entry coretype or a higher-spec member helps explain differences. The Collection remains your product identity and your billing entity; the actual coretype is operational detail you can now inspect.

How to Use​

No setup required. The attribution appears automatically on any Collection job submitted after this release. For jobs submitted on a single coretype rather than a Collection, hardware_setting and coretype_name carry the same value.

See Coretypes for full details on Coretype Collections and attribution.