<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>Amblopusa Casey 1894</title> <meta content="text/html; charset=UTF-8" http-equiv="content-type"/> </head> <body> <h1>Tribe Liparocephalini Fenyes, 1918</h1> <p> <b>Remarks.</b> Ahn (2004) and Ahn <i>et al</i>. (2010) defined the monophyletic lineage of Liparocephalini, characterized by shared character states, including the absence of seta v on the mentum, the presence of a single medial seta on the prementum, contiguous mesocoxal cavities, and the galea bearing several setae on the mesal surface and apex. Here we validate these proposed characteristics.</p> <p>Firstly, with regard to the absence of “seta v” on the mentum, it is essential to note that seta v represents one of three setae situated on the anterior margin of the mentum. Originally identified by Sawada (1970), it has proven valuable for taxonomy of the tribe Athetini. However, in Liparocephalini, the morphological variability of the mentum, when contrasted with Athetini, raises significant challenges in reliably identifying seta v (Figs. 7B, 8D, 10D, 22B). Consequently, its utility as a defining character state for asserting the tribe’s monophyly remains open to question.</p> <p> Secondly, the presence of “a single medial seta on the prementum” is not consistently observed in all Liparocephalini species. For instance, <i>Diaulota</i> and <i>Rotundicephala</i> <b>gen. n.</b> lack a medial seta (Figs. 7C, 8C, 10C, 12C, 16C), while <i>Halorhadinus</i> exhibits two medial setae (Fig. 20D), and <i>Liparocephalus</i> and <i>Paramblopusa</i> display variable numbers (0–2).</p> <p>Finally, the character states “contiguous mesocoxal cavities” and “galea with several setae exclusively on the mesal surface and apex with setae” have been refuted by Maruyama & Hayashi (2009).As a result, the morphological characteristics of Liparocephalini remain inconclusive. For further insights, refer to the discussion section.</p> </body> </html>