DOI: 10.5281/zenodo.17631244
title: IIT-CNR OFET transistor characterisation sweeps

description: OFET transistor characterisation sweeps

Sweeps of organic thin-film transistors, N- and P- types, from a series of batches fabricated in collaboration between Italian Institute of Technology, Center for Robotics and Intelligent Systems (Genova), Event-Driven Perception for Robotics group PI Chiara Bartolozzi, and Consiglio Nazionale di Ricerca, Institute for Microelectronics and Microsystems (Tor-Vergata Rome), Organic Devices group PI Luigi Mariucci.

Researchers:

Bamford, SimeonScagliotti, MattiaRapisarda, MatteoValletta, AntonioMariucci, LuigiBartolozzi, Chiara

Transistor Sweep Dataset Format

This repository contains raw transistor IDS–VGS–VDS sweep measurements.Each file corresponds to one sweep (either a VGS sweep or a VDS sweep) of a single transistor.

The dataset is designed to be simple to parse programmatically while still encoding device metadata (geometry, polarity, sweep bias) in the filename.

 



 

1. File Naming Convention

All measurement files are ASCII text files with extension .txt and names of the form:

<YYYY>_<MM>_<DD>_<hh>_<mm>_<ss>_<deviceID>_[optional CNR tokens]_<sweep tokens>_<dimension token>.txt

 

Components








Element



Description





Timestamp



First 6 underscore-separated fields: YYYY_MM_DD_hh_mm_ss





Device ID



DeviceName or CNR block form: `BL





Sweep type



A token containing IdVd → VDS sweep; otherwise → VGS sweep





Fixed bias



Vg… / Vgs… → fixed VGS; Vd… / Vds… → fixed VDS. Numerical value follows the prefix.





Polarity



_P_ → p-type; _N_ → n-type





Device geometry



Token of the form: L<length>W<width> (e.g. L50W200)






Example:

2025_03_22_14_30_05_BL_3_2_IdVd_Vg-20_L50W200.txt

 

This encodes:





timestamp = 2025-03-22 14:30:05




device = block BL, row 3, col 2




sweep type = VDS sweep




fixed Vg = −20 V




geometry: L = 50 µm, W = 200 µm



 



 

2. File Contents

Each file contains optional header lines and tab-separated numeric data.

2.1 Header lines

Lines beginning with # or V are ignored except the VDS declaration in VGS sweeps:

# Vds = <value> V

 

If present, this provides the constant VDS.If not present, the constant VDS value must be taken from the filename.

2.2 Data lines

All data lines are tab-separated floating-point numbers.

VGS sweep (sweep type = g)

<Vgs> <tab> <Ids>

 





VDS is constant for the entire file.



VDS sweep (sweep type = d)

<Vds> <tab> <Ids>

 





VGS is constant for the entire file.



 



 

3. Units





Voltages: volts (V)




Currents: amperes (A)




Channel length/width: micrometres (µm) (conventionally; units not explicitly encoded)



 



 

4. Sign Conventions





Polarity is inferred from the filename (_P_ or _N_).




p-type devices may use negative IDS and/or negative VDS.




Sign conventions are not encoded explicitly in the file and should be handled by the parser.



------------------------------------------------------------------------

5. Suggested Parsed Representation

A parser should extract for each file:

    {        "datetime": "...",        "device": "...",        "sweep_type": "g" | "d",        "fixed_vgs": <float or None>,        "fixed_vds": <float or None>,        "polarity": "p" | "n" | "?",        "length": <µm>,        "width": <µm>,        "data": [            [vgs, vds, ids],            ...        ]    }

Where: - VGS *or* VDS is constant per sweep. - `data` may be stored as apandas DataFrame or a NumPy array.

6. Importing code

For actual implementation of importer, please refer to: 

https://github.com/event-driven-robotics/ofet_import

To visualise sweeps thus imported, consider:

https://github.com/event-driven-robotics/ivplot