Optimization and tribological behavior of carbon nano tubes blended with POE oil
Bibliographic record
Abstract
Abstract Over the past two decades, nano additive lubricants have become essential in manufacturing as lubricating agents. Our study examines the impact of three process parameters—carbon nanotube (CNT) (volume concentration,%), sliding velocity (m/s), and applied load (N)—on the tribological performance of polyolester oil blended with carbon nanotubes. By employing the robust Taguchi L9 orthogonal array as the design of experiment, the current study made an attempt to identify the best combination of these three factors parameters to achieve the least coefficient of friction (COF) while the study also conducted ANOVA and multivariate linear regression to determine the significant factor that determines the least COF. For this study, POE oil and varying concentrations of CNTs (such as 0.05, 0.075 and 0.1 volume concentration%) were used. For this study, the characterization of the CNTs was performed using TEM, SEM and XRD methods while its stability was validated through Zeta potential value i.e., 0.075 volume concentration% CNT concentration achieved 35 mV zeta potential value. The Taguchi L9 orthogonal array outcomes found the least COF i.e., 0.0359 was achieved from 0.075 volume concentration % of CNT with a sliding speed of 3.6 m s−1 at 50 N load. The ANOVA outcomes confirmed the major contribution (91%) of the CNT concentration towards influencing the COF outcomes. The contour plots confirmed that optimal COF can be achieved when using 0.075 volume concentration% CNT with load ranged from 75 N to 125 N and sliding velocities between 1.2 m s−1 and 3.0 m s−1. The outcomes establish that when POE oil is supplemented with CNTs, it can achieve superior performance as the nanolubricant mitigates the coefficient of friction (COF), eventually enhancing the tribological performance. Future researchers can focus on employing Taguch-grey relational analysis, artificial intelligence and machine learning models to find the optimal process parameters for other lubricants and nanoadditives.
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.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 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".