Message Boards Message Boards

GROUPS:

Usable Property for ElementData absent from ElementData["Properties"]

Posted 9 days ago
136 Views
|
3 Replies
|
1 Total Likes
|

According to the documentation, ElementData["Properties"] gives a list of all properties available for chemical elements. However, ElementData["Properties"] does not include MolarRadioactivity despite documentation for ElementData showing that MolarRadioactibity is a usable property (Visible under the "Nuclear properties include" section). I'm asking to find out why this is the case, as it seems a bit counterintuitive.

Below, I create JSON files of the available properties when using ElementData and EntityValue.

a = ElementData["Properties"];
Export["elementData.json", a, "JSON"];

In the elementData.json file, it completely skips over MolarRadioactivity

...
"MohsHardness",
"MolarMagneticSusceptibility",
"MolarVolume",
"Name",
...

However, I can still use the property with ElementData

ElementData["Uranium", "MolarRadioactivity"]

Is this intended? If so, why? Thanks, Edwin.

Attachments:
3 Replies

Might be a bug. I would expect ElementData["Properties"] to return the same values as EntityValue["Element", "PropertyCanonicalNames"], but the latter has more and includes MolarRadioactivity.

Complement[EntityValue["Element", "PropertyCanonicalNames"],  ElementData["Properties"]]

{"CommonCompounds", "CrustMolarAbundance", "CrystalStructureImage", "DebyeCharacteristicTemperature", "ElectronCount", "FullElectronConfiguration", "HumanMolarAbundance", "Image", "IsotopeHalfLives", "IsotopeLifetimes", "KnownOxidationStates", "LewisDotStructureDiagram", "MeteoriteMolarAbundance", "MolarHeatCapacity", "MolarMass", "MolarRadioactivity", "MostCommonOxidationStates", "NeutronCount", "NuclearDiameter", "NuclearRadius", "OceanMolarAbundance", "Price", "ProtonCount", "SolarMolarAbundance", "SolidificationHeat", "SpaceGroup", "SpecificFusionHeat", "SpecificIonizationEnergies", "SpecificRadioactivity", "SpecificSolidificationHeat", "SpecificVaporizationHeat", "TensileYieldStrength", "UltimateTensileStrength", "UniverseMolarAbundance", "ValenceElectronCount", "WorkFunction"}

Posted 4 days ago

Huh. Yeah, EntityValue["Element", "PropertyCanonicalNames"] does return more values. I believe there are around 33 values that EntityValue["Element", "PropertyCanonicalNames"] returns that ElementData["Properties"] does not. And I believe there are 4 values that ElementData["Properties"] returns but EntityValue["Element", "PropertyCanonicalNames"] does not return. Normally, I wouldn't take this behavior too seriously; I only did so because MolarRadioactivity was in the documentation for ElementData["..."]. Most of the 33 previously mentioned canonical names do go through ElementData["..."], but it does through via a network request, which means it somehow uses EntityValue["Element", "..."] in the background (since other ElementData["..."] calls are near instantaneous), I believe. This slows down my script tremendously, which makes such calls impractical. Although I would appreciate if this were more explicit, there is probably some location in the documentation that I'm missing here.

when you finish entering in the missing ones, please post it !

it is likely not a bug. Mathematica "buys" data (for example, in previous versions the CRC (chemical rubber company) 5? 57th edition was used)

the data is based on experiments that company knows of (collected). it is not "calculated" is it verified as measured

it means if there is not a "reliable source" confirming the value, Mathematica will return {}

there are many things in Chemistry there are not full tables for. Mathematica used to have "very little" of CRC. it now has much more possibly not all. CRC may not be the fullest compendium of verified experimental data outcomes

I hope that helps.

Wolfram (i am not an employee) values what customers are seeking when using their product. If they think applied science is booming they will add more. They've certainly added allot recently.

Reply to this discussion
Community posts can be styled and formatted using the Markdown syntax.
Reply Preview
Attachments
Remove
or Discard

Group Abstract Group Abstract