The data in each of the following files are formatted as sets of json objects. Each one containing a unique identifier within the file, a class label if one of the training folds, and an array of time series values used for prediction. Each sample multi-variate time series has 60 values representing an observation taken at 12-minute intervals. The first value in the array is the sample observation taken at the furthest point in time from the predication period and the last value in the array is the sample observation taken at the closest point in time to the prediction period. The period of observations represented by each labeled time series is a 12 hour window of observations sliced from a longer time series.
\n\n\nSince the dataset is a set of partially overlapping sliced samples pulled from larger multi-variate time series, sampling decisions can have deleterious effects to the generalization of models trained using different strategies. For this reason, each of the training folds are temporally disjoint sets of samples so as to mitigate any possible over-fitting issues that may arise from sampling decisions made by the participants. If a standard ⅔ training ⅓ testing sampling strategy is utilized to determine a model for use as your final submission (i.e. selecting 2 folds for training and 1 fold for testing), it is guaranteed that no partially overlapping samples will be selected for both the training and testing sets and therefore the resultant trained model is more likely to generalize to the final test set used for scoring. This is not to say that using all three training folds for training your final model will not be beneficial, it is simply providing a way for participants to train/test their models independently from having to submit a result set for evaluation (which teams are limited to 2 per day), and avoid common over-fitting errors. \n
\n\nThis competition is part of the Solar Flare Prediction from Time Series of Solar Magnetic Field Parameters in the IEEE Big Data 2019 big Data Cup
\n\n\nAfter the competition phase is completed, a link for the submission of the accompanying academic paper will be provided to the top 10 participants as ranked by the public/private leaderboard weighting described on the competition website. The academic papers will be ranked by peer reviewers and a final decision will be made\tusing the weighting method detailed on the competition website.\n
\n\n\nOn behalf of the Data Mining Lab ( dmlab.cs.gsu.edu ), in the Department of Computer Science, Georgia State University, this challenge has been organized by the following.\n\n\n
The evaluation metric for this competition is FBeta-Score with Beta set to 1, which makes the score equal to the F1 score. The F1 score, commonly used in information retrieval, measures accuracy using the statistics precision p and recall r. Precision is the ratio of true positives (tp) to all predicted positives (tp + fp). Recall is the ratio of true positives to all actual positives (tp + fn). The F1 score is given by:
\n\\[ F1 = 2\\frac{p \\cdot r}{p+r}\\ \\ \\mathrm{where}\\ \\ p = \\frac{tp}{tp+fp},\\ \\ r = \\frac{tp}{tp+fn} \\]
\nThe F1 metric weights recall and precision equally, and a good retrieval algorithm will maximize both precision and recall simultaneously. Thus, moderately good performance on both will be favored over extremely good performance on one and poor performance on the other.
\n\nFor every time series sample in the testSet.json file, submission files should contain two columns: Id and ClassLabel. The ClassLabel is the class membership of each of the samples. The results are evaluated based on the Id and ClassLabel pairs. So, ordering the results by Id is not necessary.
\n\nThe file should contain a header and have the following format:
\nId,ClassLabel", "isPublished": false, "hasIsPublished": false, "postTitle": "", "hasPostTitle": false, "mimeType": "", "hasMimeType": false }, { "name": "Description", "content": "
1,1
Solar flares and Coronal Mass Ejections (CMEs) [1, 2, 3] are events occurring in the solar corona and heliosphere that can have a major negative impact on our technology dependent society [4]. Electromagnetic radiation and ionized particles from solar flares and eruptions tend to be filtered out by Earth’s atmosphere, but they can still pose a hazard to astronauts and sensitive equipment in space, as well as disrupt various high frequency radio communications that military and civilian customers become increasingly reliant upon each year. A strong enough CME can also cause significant enough fluctuations in Earth’s magnetosphere to induce currents in large networks of conductive materials such as power grids. These induced currents can lead to surges that have the potential to melt transformers of long distance transmission lines causing large scale blackouts. A 2008 report by the National Research Council concluded that a solar superstorm, similar to one observed in 1857 called the Carrington event [5], could cripple the entire US power grid for months and lead to an economic damage of 1 to 2 trillion dollars [6].
\n\nIn response, the White House released the National Space Weather Strategy and Space Weather Action Plan [4] in 2015 as a roadmap for producing research that focuses on predicting and mitigating the effects of solar eruptive activity. One of the suggested routes to accomplishing the goals set out by this roadmap was to use machine learning to predict extreme space weather events, which was reiterated recently by the current administration [7]. The goal of this dataset competition is to introduce the machine learning/data mining community to an integrated dataset that can be utilized for predicting and understanding solar flares.
\n\nThis work was supported in part by two NASA Grant Awards [No. NNX11AM13A, and No. NNX15AF39G], and one NSF Grant Award [No. AC1443061]. The NSF Grant Award has been supported by funding from the Division of Advanced Cyberinfrastructure within the Directorate for Computer and Information Science and Engineering, the Division of Astronomical Sciences within the Directorate for Mathematical and Physical Sciences, and the Division of Atmospheric and Geospace Sciences within the Directorate for Geosciences. Also, we would like to mention that all images used in this work are courtesy of NASA/SDO and the AIA, EVE, and HMI science teams.
\n\nParticipants may wish to use Kaggle API for a few important things, such as downloading the data and submitting their results. For a detailed explanation, visit kaggle-api , but for your convenience we also provide a short step-by-step tutorial here.
\n\n 1. Create a Kaggle account. (You already have this.)\n 2. Get the file `kaggle.json` which is a token, by clicking on _My Account_ > _Create New API Token_.\n 3. Place the token in your local machine in `\"~/.kaggle/kaggle.json\"` (and for Windows users in `\"C:\\Users\\