Find research datasets worth reusing
Search datasets from major research repositories and use ShareScore to quickly assess how well each record supports discovery, access, and reuse.
190
datasets available to search
ShareScore release 0.9.0
Dataset results
190 results for “equipment”
BRAIN Journal-Brain-Like Artificial Intelligence for Automation-Figure 10. Meeting Room Equipped with Different Sensors
<p>To illustrate the basic working principle of a perceptual neuro-symbolic network in a concrete application, a simplified, concrete example is given in the following. In this example, office meeting room is equipped with different sensors (tactile floor sensors, motion detectors, light barriers, a door contact sensor, a camera, and a microphone) as sketched in Figure 10.</p>
High spatiotemporal resolution free surface detection using cost-effective video equipment and computer vision techniques in nearly stationary flow along a transparent wall in the laboratory
<p>The identification of the air-water interface in free surface flows traditionally involves intrusive techniques or costly equipment. Non-intrusive alternatives, such as computer vision, are emerging as highly effective substitutes or supplements for more invasive techniques in laboratory measurements, thanks to their straightforward implementation and cost efficiency. This research specifically delves in the conjunction of various naive techniques, exploring their collective precision in detecting the air-water interface along transparent walls in laboratory. A detection technique based on the double gradient of the image is applied and thoroughly examined. The study progresses through multiple refinement stages, culminating in a method that is both cost effective and easy to implement. This methodology allows for large-scale, high resolution measurements (200 mm × 1800 frames per video at a 0.25 mm, 50 Hz resolution), offering both spatial and temporal measurements by adeptly detecting the free surface along transparent walls.</p>
Estimated stand-off distance between ADS-B equipped aircraft and obstacles
<p><strong>Summary</strong>:</p> <p>Estimated stand-off distance between ADS-B equipped aircraft and obstacles. Obstacle information was sourced from the FAA Digital Obstacle File and the FHWA National Bridge Inventory. Aircraft tracks were sourced from processed data curated from the OpenSky Network. Results are presented as histograms organized by aircraft type and distance away from runways.</p> <p> </p> <p><strong>Description:</strong></p> <p>For many aviation safety studies, aircraft behavior is represented using encounter models, which are statistical models of how aircraft behave during close encounters. They are used to provide a realistic representation of the range of encounter flight dynamics where an aircraft collision avoidance system would be likely to alert. These models currently and have historically have been limited to interactions between aircraft; they have not represented the specific interactions between obstacles and aircraft equipped transponders. In response, we calculated the standoff distance between obstacles and ADS-B equipped manned aircraft.</p> <p>For robustness, this assessment considered two different datasets of manned aircraft tracks and two datasets of obstacles. For robustness, MIT LL calculated the standoff distance using two different datasets of aircraft tracks and two datasets of obstacles. This approach aligned with the <a href="https://doi.org/10.2514/1.D0091">foundational research</a> used to support the <a href="https://doi.org/10.1520/F3442_F3442M-20">ASTM F3442/F3442M-20</a> well clear criteria of 2000 feet laterally and 250 feet AGL vertically.</p> <p>The two datasets of processed tracks of ADS-B equipped aircraft curated from the OpenSky Network. It is likely that rotorcraft were underrepresented in these datasets. There were also no considerations for aircraft equipped only with Mode C or not equipped with any transponders. The first dataset was used to train the <a href="https://github.com/Airspace-Encounter-Models/em-model-manned-bayes/releases/tag/v1.3">v1.3 uncorrelated encounter models</a> and referred to as the “Monday” dataset. The second dataset is referred to as the “aerodrome” dataset and was used to train the v2.0 and v3.x terminal encounter model. The Monday dataset consisted of 104 Mondays across North America. The other dataset was based on observations at least 8 nautical miles within Class B, C, D aerodromes in the United States for the first 14 days of each month from January 2019 through February 2020. Prior to any processing, the datasets required 714 and 847 Gigabytes of storage. For more details on these datasets, please refer to "Correlated Bayesian Model of Aircraft Encounters in the Terminal Area Given a Straight Takeoff or Landing" and “Benchmarking the Processing of Aircraft Tracks with Triples Mode and Self-Scheduling.”</p> <p>Two different datasets of obstacles were also considered. First was point obstacles defined by the FAA digital obstacle file (DOF) and consisted of point obstacle structures of antenna, lighthouse, meteorological tower (met), monument, sign, silo, spire (steeple), stack (chimney; industrial smokestack), transmission line tower (t-l tower), tank (water; fuel), tramway, utility pole (telephone pole, or pole of similar height, supporting wires), windmill (wind turbine), and windsock. Each obstacle was represented by a cylinder with the height reported by the DOF and a radius based on the report horizontal accuracy. We did not consider the actual width and height of the structure itself. Additionally, we only considered obstacles at least 50 feet tall and marked as verified in the DOF.</p> <p>The other obstacle dataset, termed as “bridges,” was based on the identified bridges in the FAA DOF and additional information provided by the National Bridge Inventory. Due to the potential size and extent of bridges, it would not be appropriate to model them as point obstacles; however, the FAA DOF only provides a point location and no information about the size of the bridge. In response, we correlated the FAA DOF with the National Bridge Inventory, which provides information about the length of many bridges. Instead of sizing the simulated bridge based on horizontal accuracy, like with the point obstacles, the bridges were represented as circles with a radius of the longest, nearest bridge from the NBI. A circle representation was required because neither the FAA DOF or NBI provided sufficient information about orientation to represent bridges as rectangular cuboid. Similar to the point obstacles, the height of the obstacle was based on the height reported by the FAA DOF. Accordingly, the analysis using the bridge dataset should be viewed as risk averse and conservative. It is possible that a manned aircraft was hundreds of feet away from an obstacle in actuality but the estimated standoff distance could be significantly less. Additionally, all obstacles are represented with a fixed height, the potentially flat and low level entrances of the bridge are assumed to have the same height as the tall bridge towers. The attached figure illustrates an example simulated bridge.</p> <p>It would had been extremely computational inefficient to calculate the standoff distance for all possible track points. Instead, we define an encounter between an aircraft and obstacle as when an aircraft flying 3069 feet AGL or less comes within 3000 feet laterally of any obstacle in a 60 second time interval. If the criteria were satisfied, then for that 60 second track segment we calculate the standoff distance to all nearby obstacles. Vertical separation was based on the MSL altitude of the track and the maximum MSL height of an obstacle.</p> <p>For each combination of aircraft track and obstacle datasets, the results were organized seven different ways. Filtering criteria were based on aircraft type and distance away from runways. Runway data was sourced from the FAA runways of the United States, Puerto Rico, and Virgin Islands <a href="https://adds-faa.opendata.arcgis.com/datasets/4d8fa46181aa470d809776c57a8ab1f6_0/about">open dataset</a>. Aircraft type was identified as part of the <a href="https://github.com/Airspace-Encounter-Models/em-processing-opensky">em-processing-opensky</a> workflow.</p> <ul> <li><em>All</em>: No filter, all observations that satisfied encounter conditions</li> <li><em>nearRunway</em>: Aircraft within or at 2 nautical miles of a runway</li> <li><em>awayRunway</em>: Observations more than 2 nautical miles from a runway</li> <li><em>glider</em>: Observations when aircraft type is a glider</li> <li><em>fwme</em>: Observations when aircraft type is a fixed-wing multi-engine</li> <li><em>fwse</em>: Observations when aircraft type is a fixed-wing single engine</li> <li><em>rotorcraft</em>: Observations when aircraft type is a rotorcraft</li> </ul> <p><strong>License</strong></p> <p>This dataset is licensed under Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International(CC BY-NC-ND 4.0).</p> <p>This license requires that reusers give credit to the creator. It allows reusers to copy and distribute the material in any medium or format in unadapted form and for noncommercial purposes only. Only noncommercial use of your work is permitted. Noncommercial means not primarily intended for or directed towards commercial advantage or monetary compensation. Exceptions are given for the not for profit standards organizations of ASTM International and RTCA.</p> <p>MIT is releasing this dataset in good faith to promote open and transparent research of the low altitude airspace. Given the limitations of the dataset and a need for more research, a more restrictive license was warranted. Namely it is based only on only observations of ADS-B equipped aircraft, which not all aircraft in the airspace are required to employ; and observations were source from a crowdsourced network whose surveillance coverage has not been robustly characterized.</p> <p>As more research is conducted and the low altitude airspace is further characterized or regulated, it is expected that a future version of this dataset may have a more permissive license.</p> <p><strong>Distribution Statement</strong></p> <p>DISTRIBUTION STATEMENT A. Approved for public release. Distribution is unlimited.</p> <p>© 2021 Massachusetts Institute of Technology.</p> <p>Delivered to the U.S. Government with Unlimited Rights, as defined in DFARS Part 252.227-7013 or 7014 (Feb 2014). Notwithstanding any copyright notice, U.S. Government rights in this work are defined by DFARS 252.227-7013 or DFARS 252.227-7014 as detailed above. Use of this work other than as specifically authorized by the U.S. Government may violate any copyrights that exist in this work.</p> <p>This material is based upon work supported by the Federal Aviation Administration under Air Force Contract No. FA8702-15-D-0001. Any opinions, findings, conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the Federal Aviation Administration.</p> <p>This document is derived from work done for the FAA (and possibly others); it is not the direct product of work done for the FAA. The information provided herein may include content supplied by third parties. Although the data and information contained herein has been produced or processed from sources believed to be reliable, the Federal Aviation Administration makes no warranty, expressed or implied, regarding the accuracy, adequacy, completeness, legality, reliability or usefulness of any information, conclusions or recommendations provided herein. Distribution of the information contained herein does not constitute an endorsement or warranty of the data or information provided herein by the Federal Aviation Administration or the U.S. Department of Transportation. Neither the Federal Aviation Administration nor the U.S. Department of Transportation shall be held liable for any improper or incorrect use of the information contained herein and assumes no responsibility for anyone’s use of the information. The Federal Aviation Administration and U.S. Department of Transportation shall not be liable for any claim for any loss, harm, or other damages arising from access to or use of data or information, including without limitation any direct, indirect, incidental, exemplary, special or consequential damages, even if advised of the possibility of such damages. The Federal Aviation Administration shall not be liable to anyone for any decision made or action taken, or not taken, in reliance on the information contained herein.</p> <p><strong>Download and Format:</strong></p> <p>The dataset is provided as a single .zip archive with multiple directories. The directories indicate the aircraft track dataset and types of obstacles. Within each directory are csv files corresponding to different the filtering criteria. These files are the total counts of observations (histogram) where columns corresponding to lateral (range) distance between the simulated obstacle and aircraft and rows correspond to the relative vertical separation. The files centers_x_ft.csv and centers_y_ft.csv are the center of each bin.</p> <p>Simply download the .zip file and extract. The MD5 checksum of the .zip file prior to uploading to Zenodo was 03e5aed725a4cf393683730e05521ba5.</p> <p><strong>MIT Lincoln Laboratory LL Group and Division this dataset is associated with</strong>:</p> <ul> <li>Group 42 / Division 4</li> <li>Topic: collision avoidance</li> <li>R&D Area: Air Traffic Control</li> <li>R&D Group: Surveillance Systems</li> </ul>
A Semantically Annotated 15-Class Ground Truth Dataset for Substation Equipment
<p>This dataset contains 1660 images of electric substations with 50705 annotated objects. The images were obtained using different cameras, including cameras mounted on Autonomous Guided Vehicles (AGVs), fixed location cameras and those captured by humans using a variety of cameras. A total of 15 classes of objects were identified in this dataset, and the number of instances for each class is provided in the following table:</p> <table align="center"> <caption>Object classes and how many times they appear in the dataset.</caption> <thead> <tr> <th scope="col">Class</th> <th scope="col">Instances</th> </tr> </thead> <tbody> <tr> <td>Open blade disconnect</td> <td>310</td> </tr> <tr> <td>Closed blade disconnect switch</td> <td>5243</td> </tr> <tr> <td>Open tandem disconnect switch</td> <td>1599</td> </tr> <tr> <td>Closed tandem disconnect switch</td> <td>966</td> </tr> <tr> <td>Breaker</td> <td>980</td> </tr> <tr> <td>Fuse disconnect switch</td> <td>355</td> </tr> <tr> <td>Glass disc insulator</td> <td>3185</td> </tr> <tr> <td>Porcelain pin insulator</td> <td>26499</td> </tr> <tr> <td>Muffle</td> <td>1354</td> </tr> <tr> <td>Lightning arrester</td> <td>1976</td> </tr> <tr> <td>Recloser</td> <td>2331</td> </tr> <tr> <td>Power transformer</td> <td>768</td> </tr> <tr> <td>Current transformer</td> <td>2136</td> </tr> <tr> <td>Potential transformer</td> <td>654</td> </tr> <tr> <td>Tripolar disconnect switch</td> <td>2349</td> </tr> </tbody> </table> <p>All images in this dataset were collected from a single electrical distribution substation in Brazil over a period of two years. The images were captured at various times of the day and under different weather and seasonal conditions, ensuring a diverse range of lighting conditions for the depicted objects. A team of experts in Electrical Engineering curated all the images to ensure that the angles and distances depicted in the images are suitable for automating inspections in an electrical substation.</p> <p>The file structure of this dataset contains the following directories and files:</p> <p> images: This directory contains 1660 electrical substation images in JPEG format.</p> <p>images: This directory contains 1660 electrical substation images in JPEG format.</p> <ul> <li><strong>labels_json: </strong>This directory contains JSON files annotated in the VOC-style polygonal format. Each file shares the same filename as its respective image in the images directory.</li> <li><strong>15_masks:</strong> This directory contains PNG segmentation masks for all 15 classes, including the porcelain pin insulator class. Each file shares the same name as its corresponding image in the images directory.</li> <li><strong>14_masks:</strong> This directory contains PNG segmentation masks for all classes except the porcelain pin insulator. Each file shares the same name as its corresponding image in the images directory.</li> <li><strong>porcelain_masks:</strong> This directory contains PNG segmentation masks for the porcelain pin insulator class. Each file shares the same name as its corresponding image in the images directory.</li> <li><strong>classes.txt:</strong> This text file lists the 15 classes plus the background class used in LabelMe.</li> <li><strong>json2png.py:</strong> This Python script can be used to generate segmentation masks using the VOC-style polygonal JSON annotations.</li> </ul> <p>The dataset aims to support the development of computer vision techniques and deep learning algorithms for automating the inspection process of electrical substations. The dataset is expected to be useful for researchers, practitioners, and engineers interested in developing and testing object detection and segmentation models for automating inspection and maintenance activities in electrical substations.</p> <p>The authors would like to thank UTFPR for the support and infrastructure made available for the development of this research and COPEL-DIS for the support through project PD-2866-0528/2020—Development of a Methodology for Automatic Analysis of Thermal Images. We also would like to express our deepest appreciation to the team of annotators who worked diligently to produce the semantic labels for our dataset. Their hard work, dedication and attention to detail were critical to the success of this project.</p>
NEW REFERENCE HVDC DIVIDER FOR THE CALIBRATION OF TESTING EQUIPMENT UP TO 1600 kV
<p>An international metrology project named “EMPIR 19ENG02 FutureEnergy” started in June 2020, is developing, building, and evaluating measurement equipment and systems for the UHV level. This paper describes the work on a new reference UHVDC voltage divider for the calibration of testing equipment up to at least 1600 kV. This divider has a modular design and target expanded measurement uncertainty of 200 μV/V. The need for such measurement systems results from new measurement methods for future energy transmission grids. After the construction of the UHVDC voltage divider, the targeted measurement uncertainty of 200 μV/V was successfully at 1200 kV during a measurement campaign at PTB. The linearity and temperature dependence of the UHVDC divider modules as well as the overall results of this new divider are included in this work. This work will lead to new calibration and measurement capabilities (CMC) for traceability of the designed divider systems for participating national metrology institutes (NMI).</p>
"I was on vacation in Mala, living in a self-catering holiday cottage, together with my girlfriend (we're together for 11 years now), recovering from a heavy workload in the second half of 2008. We were sitting outside, probably sipping a beer, when we heard the sound of bells approaching. Stepping on the stones that enclose the little forecourt of the cottage, we could just see the goat herd being driven by. Idashed for my R09 (recording equipment) to get that impression – but too slowly too late, it seemed, the herd had disappeared and with it the sound. When Iwas about to pack my R09 again the sound appeared to come back, so Idashed down the driveway, just in time to see the herd pass, and then Ifollowed it a couple of hundred meters, walking behind the herd, trying not to breathe or make stepping sounds, eventually, when dogs started barking and a car approached from behind, I stopped and let the goats go on, the car passes, honks ... and Icut the recording and walk back to the cottage." [Peter/ptroxler]13 in Collecting Sounds. Online Sharing of Field Recordings as Cultural Practice
"I was on vacation in Mala, living in a self-catering holiday cottage, together with my girlfriend (we're together for 11 years now), recovering from a heavy workload in the second half of 2008. We were sitting outside, probably sipping a beer, when we heard the sound of bells approaching. Stepping on the stones that enclose the little forecourt of the cottage, we could just see the goat herd being driven by. Idashed for my R09 (recording equipment) to get that impression – but too slowly too late, it seemed, the herd had disappeared and with it the sound. When Iwas about to pack my R09 again the sound appeared to come back, so Idashed down the driveway, just in time to see the herd pass, and then Ifollowed it a couple of hundred meters, walking behind the herd, trying not to breathe or make stepping sounds, eventually, when dogs started barking and a car approached from behind, I stopped and let the goats go on, the car passes, honks ... and Icut the recording and walk back to the cottage." [Peter/ptroxler]13
Data from: A laser-equipped tunnel for the assessment of multiple burst swimming traits in fishes
Open the record for dataset details and reuse information.
A 2.5-year campus-level smart meter database with equipment data for energy analytics
Open the record for dataset details and reuse information.
Funerary equipment
Part of a grave marker. Date: 400 B.C. — 301 B.C. Period: Classical Description: grave loutrophoros Material: marble (Pentelic) Dimension(s): height, 0.681, m width, 0.325, m weight, 165, kg, approx. Acquisition: bequeathed; 1885; Worsley, Thomas Object Number: GR.1b.1885 (Antiquities) https://data.fitzmuseum.cam.ac.uk/id/object/66016 Source: Objaverse 1.0 / Sketchfab
Using Old Laboratory Equipment with Modern Web-of-Things Standards: a Smart Laboratory with LabThings Retro. Supplementary material - Video demonstration
<p>Supplementary Material for 'Using Old Laboratory Equipment with Modern Web-of-Things Standards: a Smart Laboratory with LabThings Retro'. </p><p>Video demonstration for LabThings Retro. </p><p>This video has no sound.</p>
Ballista - Siege Equipment Assets
One of my many siege equipment I'm making for the Real-Time Design Challenge: Medieval Fantasy! Source: Objaverse 1.0 / Sketchfab
Siege Tower - Siege Equipment Assets
The good old siege tower, this guy was awesome to make! Created for the medieval fantasy challenge, I used two different designs to concept this guy. Source: Objaverse 1.0 / Sketchfab
Laser-equipped gas reaction chamber for probing environmentally sensitive materials at near atomic scale
<p>Five atom probe datasets as featured in the PLOSone journal concerning the methodology of laser-assisted thermochemical gas treatments of atom probe needles, two comparing the deuterium charged and uncharged states of a steel and comparing various early states of direct hydrogen reduction of FeO.</p>
Resource Guide for State DOT's Maintenance Equipment Fleet Management Decisions
<p>This research created a guide for state Departments of Transportation fleet management on utilizing equipment fleet management system data to make informed fleet management decisions. The research team took the historical equipment fleet data from the Oklahoma Department of Transportation and developed workflows, algorithms, and examples to demonstrate the use of historical equipment data for equipment decisions. Specifically, the research team demonstrated 1) the use of life cycle analysis and dynamic programming models for equipment replacement decisions; 2) developed algorithms to calculate equipment rental rates that can be used by the Department to forecast and allocate equipment operational budget among field districts and central office, 3) developed a procedure to make own-rent/lease decisions based on historical equipment management data. Using the two class codes of equipment (Class Code 5355 – 2 Yd. front-end loaders and Class Code 5385 – 1/2-ton fleetside pickup trucks) as examples, the research team presented the result of the equipment replacement models using both life cycle analysis and dynamic programming approaches and discussed the difference of those two methods. In addition, the impact of model input parameters (specifically depreciation cost estimation using both straight line and double declining balance depreciation calculation methods) on equipment replacement outcomes is discussed. The framework for deciding between on renting or owning for the two class codes of equipment was developed. Also, the equipment rental rates for the most frequently used equipment by ODOT were updated per class code.</p>
Personal Protective Equipment Dataset (PPED)
<p><strong>Personal Protective Equipment Dataset (PPED)</strong></p> <p>This dataset serves as a benchmark for PPE in chemical plants<br> We provide datasets and experimental results.</p> <p><strong>1. The dataset</strong></p> <p>We produced a data set based on the actual needs and relevant regulations in chemical plants.<br> The standard GB 39800.1-2020 formulated by the Ministry of Emergency Management of the People’s Republic of China defines the protective requirements for plants and chemical laboratories.<br> The complete dataset is contained in the folder <code>PPED/data</code>.</p> <p><strong>1.1. Image collection</strong></p> <p>We took more than 3300 pictures.<br> We set the following different characteristics, including different environments, different distances, different lighting conditions, different angles, and the diversity of the number of people photographed.</p> <ul> <li>Backgrounds: There are 4 backgrounds, including office, near machines, factory and regular outdoor scenes.</li> <li>Scale: By taking pictures from different distances, the captured PPEs are classified in small, medium and large scales.</li> <li>Light: Good lighting conditions and poor lighting conditions were studied.</li> <li>Diversity: Some images contain a single person, and some contain multiple people.</li> <li>Angle: The pictures we took can be divided into front and side.</li> </ul> <p>A total of more than 3300 photos were taken in the raw data under all conditions.<br> All images are located in the folder “PPED/data/JPEGImages”.</p> <p><strong>1.2. Label</strong></p> <p>We use Labelimg as the labeling tool, and we use the PASCAL-VOC labelimg format.<br> Yolo use the txt format, we can use <code>trans_voc2yolo.py</code> to convert the XML file in PASCAL-VOC format to txt file.<br> Annotations are stored in the folder <code>PPED/data/Annotations</code></p> <p><strong>1.3. Dataset Features</strong></p> <p>The pictures are made by us according to the different conditions mentioned above.<br> The file <code>PPED/data/feature.csv</code> is a CSV file which notes all the .os of all the image. It records every feature of the picture, including lighting conditions, angles, backgrounds, number of people and scale.</p> <p>1.4. Dataset Division</p> <p>The data set is divided into 9:1 training set and test set.</p> <p><strong>2. Baseline Experiments</strong></p> <p>We provide baseline results with five models, namely Faster R-CNN ®, Faster R-CNN (M), SSD, YOLOv3-spp, and YOLOv5.<br> All code and results is given in folder <code>PPED/experiment</code>.</p> <p><strong>2.1. Environment and Configuration:</strong></p> <ul> <li>Intel Core i7-8700 CPU</li> <li>NVIDIA GTX1060 GPU</li> <li>16 GB of RAM</li> <li>Python: 3.8.10</li> <li>pytorch: 1.9.0</li> <li>pycocotools: pycocotools-win</li> <li>Windows 10</li> </ul> <p><strong>2.2. Applied Models</strong></p> <p>The source codes and results of the applied models is given in folder <code>PPED/experiment</code> with sub-folders corresponding to the model names.</p> <p><strong>2.2.1. Faster R-CNN</strong></p> <ul> <li>Faster R-CNN <ul> <li>backbone: resnet50+fpn <ul> <li>We downloaded the pre-training weights from <a href="https://download.pytorch.org/models/fasterrcnn_resnet50_fpn_coco-258fb6c6.pth">https://download.pytorch.org/models/fasterrcnn_resnet50_fpn_coco-258fb6c6.pth</a>.</li> <li>We modified the dataset path, training classes and training parameters including batch size.</li> <li>We run <code>train_res50_fpn.py</code> start training.</li> <li>Then, the weights are trained by the training set.</li> <li>Finally, we validate the results on the test set.</li> </ul> </li> <li>backbone: mobilenetv2 <ul> <li>the same training method as resnet50+fpn, but the effect is not as good as resnet50+fpn, so it is directly discarded.</li> </ul> </li> </ul> </li> </ul> <p>The Faster R-CNN source code used in our experiment is given in folder <code>PPED/experiment/Faster R-CNN</code>.<br> The weights of the fully-trained Faster R-CNN (R), Faster R-CNN (M) model are stored in file <code>PPED/experiment/trained_models/resNetFpn-model-19.pth and </code>mobile-model.pth.<br> The performance measurements of Faster R-CNN (R) Faster R-CNN (M) are stored in folder <code>PPED/experiment/results/Faster RCNN(R)and Faster RCNN(M)</code>.</p> <p><strong>2.2.2. SSD</strong></p> <ul> <li>backbone: resnet50</li> <li>We downloaded pre-training weights from <a href="https://download.pytorch.org/models/resnet50-19c8e357.pth">https://download.pytorch.org/models/resnet50-19c8e357.pth</a>.</li> <li>The same training method as Faster R-CNN is applied.</li> </ul> <p>The SSD source code used in our experiment is given in folder <code>PPED/experiment/ssd</code>.<br> The weights of the fully-trained SSD model are stored in file <code>PPED/experiment/trained_models/SSD_19.pth</code>.<br> The performance measurements of SSD are stored in folder <code>PPED/experiment/results/SSD</code>.</p> <p><strong>2.2.3. YOLOv3-spp</strong></p> <ul> <li>backbone: DarkNet53</li> <li>We modified the type information of the XML file to match our application.</li> <li>We run <code>trans_voc2yolo.py</code> to convert the XML file in VOC format to a txt file.</li> <li>The weights used are: yolov3-spp-ultralytics-608.pt.</li> </ul> <p>The YOLOv3-spp source code used in our experiment is given in folder <code>PPED/experiment/YOLOv3-spp</code>.<br> The weights of the fully-trained YOLOv3-spp model are stored in file <code>PPED/experiment/trained_models/YOLOvspp-19.pt</code>.<br> The performance measurements of YOLOv3-spp are stored in folder <code>PPED/experiment/results/YOLOv3-spp</code>.</p> <p><strong>2.2.4. YOLOv5</strong></p> <ul> <li>backbone: CSP_DarkNet</li> <li>We modified the type information of the XML file to match our application.</li> <li>We run <code>trans_voc2yolo.py</code> to convert the XML file in VOC format to a txt file.</li> <li>The weights used are: yolov5s.</li> </ul> <p>The YOLOv5 source code used in our experiment is given in folder <code>PPED/experiment/yolov5</code>.<br> The weights of the fully-trained YOLOv5 model are stored in file <code>PPED/experiment/trained_models/YOLOv5.pt</code>.<br> The performance measurements of YOLOv5 are stored in folder <code>PPED/experiment/results/YOLOv5</code>.</p> <p>2.3. Evaluation</p> <p>The computed evaluation metrics as well as the code needed to compute them from our dataset are provided in the folder <code>PPED/experiment/eval</code>.</p> <p><strong>3. Code Sources</strong></p> <ol> <li>Faster R-CNN (R and M) <ul> <li>https://github.com/WZMIAOMIAO/deep-learning-for-image-processing/tree/master/pytorch_object_detection/faster_rcnn</li> <li>official code: https://github.com/pytorch/vision/blob/main/torchvision/models/detection/faster_rcnn.py</li> </ul> </li> <li>SSD <ul> <li><a href="https://github.com/WZMIAOMIAO/deep-learning-for-image-processing/tree/master/pytorch_object_detection/ssd">https://github.com/WZMIAOMIAO/deep-learning-for-image-processing/tree/master/pytorch_object_detection/ssd</a></li> <li>official code: <a href="https://github.com/pytorch/vision/blob/main/torchvision/models/detection/ssd.py">https://github.com/pytorch/vision/blob/main/torchvision/models/detection/ssd.py</a></li> </ul> </li> <li>YOLOv3-spp <ul> <li><a href="https://github.com/WZMIAOMIAO/deep-learning-for-image-processing/tree/master/pytorch_object_detection/yolov3-spp">https://github.com/WZMIAOMIAO/deep-learning-for-image-processing/tree/master/pytorch_object_detection/yolov3-spp</a></li> </ul> </li> <li>YOLOv5 <ul> <li><a href="https://github.com/ultralytics/yolov5">https://github.com/ultralytics/yolov5</a></li> </ul> </li> </ol>
Numerical analysis of working paper "Joint integrated production-maintenance policy of a deteriorating equipment considering random yield and maintenance delay"
<p>This is the numerical analysis code using in the working paper "Joint integrated production-maintenance policy of a</p> <p>deteriorating equipment considering random yield and maintenance delay"</p>
Mangonel - Siege Equipment Assets
A Mangonel I created for the medieval fantasy challenge! I had a lot of fun creating this one, and I'm very happy with how it turned out! Source: Objaverse 1.0 / Sketchfab
Project EQuIP: Empowering Queer Identities in Psychotherapy
ClinicalTrials.gov study NCT03721276. IPD Sharing: NO. Countries: 1. Publications: 10.
The Effectiveness of Health Education Intervention in Enhancing Personal Protective Equipment Use
ClinicalTrials.gov study NCT07087444. IPD Sharing: YES. Countries: 1. Publications: 1.
Implementing Effective, Collaborative Care for Schizophrenia (EQUIP-2)
ClinicalTrials.gov study NCT00137280. IPD Sharing: NO. Countries: 1. Publications: 7.
ScienceDex guides
Understand access before you commit
These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.
Allen Brain Atlas
Allen Brain Atlas is an Allen Institute collection of brain map atlases, datasets, APIs, and analysis tools covering mouse, human, and non-human primate brain resources.
Annotated Behaviour and Observability Dataset (ABODe)
ABODe is a University of Edinburgh DataShare dataset for behavior classification in group-housed mice using home-cage video, identities, bounding boxes, ground-plate positions, and annotator labels.
DANDI Archive for NWB datasets
DANDI is a BRAIN Initiative archive for publishing and sharing neurophysiology data, including electrophysiology, optophysiology, and behavioral data packaged as NWB and related standards.
International Brain Laboratory public data
The International Brain Laboratory public data releases expose standardized mouse decision-making experiments, including Neuropixels recordings, widefield calcium imaging, behavior, and session metadata accessed through the ONE API.
OpenNeuro
OpenNeuro is a free, open platform for sharing neuroimaging datasets, with public search, dataset pages, and download paths for web, S3, DataLad, and the OpenNeuro CLI.