3D inversion of magnetic data seeking sharp boundaries: a case study for a porphyry copper deposit from Now Chun in central Iran
Bibliographic record
Abstract
ABSTRACT This paper describes an application of 3D inversion of magnetic data to recover a susceptibility model from magnetic anomalies. For this purpose, the subsurface of the desired area of the magnetic anomaly is divided into a mesh with a large number of rectangular prisms with unknown susceptibilities. A Tikhonov cost function with multi‐term regularizers involving boundaries of susceptibility distribution and an edge‐preserving penalty function, as a tool to recover sharp boundaries, was used. Three methods (i.e., the U‐curve, Tikhonov‐curve and L‐curve methods) are applied to determine the optimum regularization parameter during the inversion process. Testing of the applied methods showed that the application of the U‐curve (a well‐known method in applied mathematics) in geophysical inverse problems and Tikhonov‐curve as a proposed technique can be appropriate candidates, like a common L‐curve method, for choosing the optimal regularization parameter. To avoid the natural tendency of magnetic structures to concentrate at the shallow depths in models created by inversion, a depth weighting function derived from information of the depth‐to‐the‐bottom of a generating source was applied. The AN‐EUL technique as a combination of the analytic signal and the Euler deconvolution methods is used to estimate the structural index of causative sources in order to construct an appropriate depth weighting function. Here, it is assumed that there is no remanent magnetization and the observed data are influenced by only the induced magnetization. A case study involving ground based measurements over a porphyry‐Cu deposit located in Kerman providence of Iran, Now Chun deposit, is included. The recovered 3D susceptibility model provided beneficial information for design of the exploration drilling programme. The susceptibility lows in the constructed model, in particular, their depths down to 410 m, coincides with the known locations of copper mineralization.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".