

<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type='text/xsl' href='/oai.xsl' ?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/
	http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
<responseDate>2026-02-16T08:47:04Z</responseDate>
<request verb="ListRecords" metadataPrefix="oai_dc" identifier="oai:publications.copernicus.org:acp30709">http:///OAfile/jner-1536984.</request>
	<ListRecords>
	<record>
	<header>
		<identifier>/OAfile/jner-1536984xsd</identifier>

		<datestamp>2025-01-01 </datestamp>
		<setSpec>acp</setSpec>
		</header>
		<metadata>
		<oai_dc:dc
			xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
			xmlns:dc="http://purl.org/dc/elements/1.1/"
			xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
			xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
			http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
			<dc:title><![CDATA[YOLO-Based Deep Learning Approach for Turkish Sign Language Recognition]]></dc:title>
			<dc:creator>İLİSULU*,Ahmet</dc:creator>
			<dc:creator>KUTLU,Yakup</dc:creator>
			<dc:description><![CDATA[We actually undertook this project based on a very simple need: to alleviate some of the difficulties hearing-impaired individuals experience when expressing themselves. While thinking about how to make TID more understandable, it made sense to incorporate artificial intelligence. YOLO models are already well known for their speed and practicality, so we went straight for them. We prepared a total dataset of 9,534 images. We added not only the basic signs we knew but also signs like “Hurry up” and “Help me,” which would be useful in emergencies in daily life. Because these are the things that are actually needed in real life. YOLOv11s was very fast but a bit weak in terms of accuracy. So it works, but not quite at the level we wanted. YOLOv8m was great in terms of accuracy, but it really took its toll on the system; it was slow and training took a long time. YOLOv11m, on the other hand, struck the perfect balance. It wasn&#39;t too slow or too cumbersome. It delivered very clean results with 0.993 mAP50 and 0.991 F1-Score. In short, we decided that YOLOv11m is the most logical choice for a real-time application. It&#39;s both fast and sufficiently accurate.]]></dc:description>
			<dc:date>2025-01-01</dc:date>
			<dc:type>Text</dc:type>
			<dc:format>application/pdf</dc:format>
			<dc:identifier>-</dc:identifier>
			<dc:identifier>-</dc:identifier>
			<dc:source>-</dc:source>
			<dc:language>eng</dc:language>
		</oai_dc:dc>
	</metadata>
	</record>
</ListRecords>
</OAI-PMH>

