Skip to content

derived_properties no longer exists #136

Description

@Bud-Macaulay

This endpoint that was attached is no longer in existance.

I think in principle this is fine; however we should be sure to test what this drops. In particular as of current, i was using derived properties to build some visualisers:

structureData:

  const hasDerived =
    nodeData.derived_properties &&
    Object.keys(nodeData.derived_properties).length > 0;

  const lattice = nodeData.attributes?.cell || null;
  const latticeLengths = lattice ? formatLattice(nodeData) : null;
  const volume = hasDerived
    ? nodeData.derived_properties.dimensionality?.value
    : latticeLengths
      ? getVol(nodeData)
      : null;
  const sites = nodeData.attributes?.sites || [];
  const kinds = nodeData.attributes?.kinds || [];
  const numSites = sites.length;
  const dimensionality =
    nodeData.derived_properties?.dimensionality?.dim || null;

KpointsData

    const attrs = nodeData.attributes || {};
    const derived = nodeData.derived_properties || {};

    let b1 = null,
      b2 = null,
      b3 = null;
    if (attrs.cell) {
      [b1, b2, b3] = reciprocalLattice(attrs.cell);
    }

    const bz = attrs.cell
      ? {
          ...derived,
          b1,
          b2,
          b3,
          kpoints: derived.labelled_kpoints_abs,
          path: derived.labelled_path,
        }
      : null;

In particular the KpointsData was being used quite extensively to visualise the brillioun zone and other things. I wouldnt be shocked if the compute for these was expensive and maybe we should not default to this.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Fields

Priority

None yet

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions