Ree mobility and tetrad effects in bauxites an example from the Kanisheeteh deposit, NW Iran

Title:

Ree mobility and tetrad effects in bauxites an example from the Kanisheeteh deposit, NW Iran

Creator:

Abedini , Ali, Rezaei Azizi , Mansour , and Calagari, Ali Asghar

Identifier:

https://cdk.lib.cas.cz/client/handle/uuid:b8f6c33f-0fa9-4973-aa60-419634f63bf3
uuid:b8f6c33f-0fa9-4973-aa60-419634f63bf3
doi:10.13168/AGG.2019.0002

Subject:

REE, Mobility, Tetrad-effect, Bauxite, Kanisheeteh, and Iran

Type:

model:article and TEXT

Format:

bez média and svazek

Description:

The Kanisheeteh bauxite deposit (NW Iran) is located on the Irano-Himalaya karst bauxite belt and was developed as stratiform horizon along the contact of the Permian and Triassic formations. Based on absolute weathering index (AWI), HREE were leached out, whereas LREE suffered both leaching and fixation during bauxitization. The non-CHARAC characteristic of Y/Ho ratios can be attributed to geochemically known phenomenon as the "tetrad effect". The simultaneous convex and concave curves of the tetrad effect were observed in the chondrite-normalized REE patterns of the bauxite ores. The correlation between the sizes of T4 and AWI% values revealed two separate populations. The first one is characterized by a wide variation in sizes of T4 and very narrow AWI% values, and is thought to be related to acidic zone of the profile. In contrast, the second one is marked by a narrow variation in sizes of T4 and wide variation in AWI% values, and is conceived to be affiliated to alkaline zone of the profile. In this research, the tetrad effect proved to be capable of clarifying the geochemical characteristics of the deposit and can be applied as a good geochemical index to investigate the prevailed paleo-conditions of depositional environments.

Language:

English

Rights:

http://creativecommons.org/publicdomain/mark/1.0/
policy:public

Coverage:

11-26

Source:

Acta geodynamica et geomaterialia : | 2019 Volume:16 | Number:1 (193)

Harvested from:

CDK

Metadata only:

false