You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This database is created from a database of semiconductor band gap records, released for [Dong, Q., & Cole, J. M. (2022). Auto-generated database of semiconductor band gaps using chemdataextractor. Scientific Data, 9(1), 193.](https://www.nature.com/articles/s41597-022-01294-6). This work presents an auto-generated database of 100236 semiconductor band gap records, extracted from 128776 journal articles with their associated temperature information. The database was produced using ChemDataExtractor version 2.0.
8
+
9
+
10
+
There were 100236 records in the database before processing and only a few records after executing the pipeline. This is mainly due to values shifting with the invalid formatting of the source CSV. Many rows include a line break in the "Text" column, making the formatting of the CSV file invalid. Future work in Jayvee should add the functionality to remove those line breaks.
Copy file name to clipboardExpand all lines: src/models/14079863/SemiconductorBandGapsModel.jv
+2-30Lines changed: 2 additions & 30 deletions
Original file line number
Diff line number
Diff line change
@@ -1,31 +1,3 @@
1
-
/*
2
-
This database is created from the paper cited as "Dong, Q., & Cole, J. M. (2022). Auto-generated database of semiconductor band gaps using chemdataextractor. Scientific Data, 9(1), 193.". This work presents an
3
-
auto-generated database of 100,236 semiconductor band gap records, extracted from 128,776 journal articles with their associated temperature information. The database was produced using
4
-
ChemDataExtractor version 2.0, a ‘chemistry-aware’ software toolkit. Evaluation of the database shows a weighted precision of 84% and a weighted recall of 65%.
5
-
6
-
There were 100236 records in the database before the data engineering pipeline and only 29 records after executing the pipeline. The big difference in no. of rows is because of the fact that most of the rows in
7
-
the column "Composition" is null, which cannot be the case for this dataset. We have removed all such records where the "Composition" is null. Other than that for multiple rows like Temperature_value, Temperature_Unit, the values have shifted to the adjacent columns. As a result,
8
-
we have treated all those rows as noise and filtered out all such data points. This is the major reason behind the reduction in no. of records before and after the pipeline.
9
-
10
-
Our other changes include: removing opening ("[") and closing ("]") braces from the numerical values like "Value", "Temperature_Value", removeing "(" and ")" from "Raw_Unit", standardizing the DOI Reference column to
11
-
a standard foramt of 10.1007/xxxx, and adding "AllowedListConstraint" to "TemperatureUnitType".
12
-
13
-
All the changes have been mentioned in details right before the part of the code that is responsible to cause these changes in the pipeline.
14
-
*/
15
-
16
-
17
-
// Removed white spaces from the Composition formula and kept only those rows in the format of {'element_scientific_name': units}
0 commit comments