Retrieving a contingency table from a correspondence analysis solution

DOI10.1016/J.EJOR.2019.11.014MaRDI QIDQ2286973zbMATH OpenOpenAlexWikidataFDO

Authors Michel Van De Velden, Wilco van den Heuvel, Hugo Galy, Patrick J. F. Groenen

Publication date 23 January 2020

Published in European Journal of Operational Research (Search for Journal in Brave)

Full work available at URL https://doi.org/10.1016/j.ejor.2019.11.014

zbMATH Keywords

correspondence analysisinteger programminginverse problemsmultivariate statistics

Mathematics Subject Classification ID

Contingency tables (62H17) Factor analysis and principal components; correspondence analysis (62H25) Linear programming (90C05) Integer programming (90C10)

Recommendations

• Inverse correspondence analysis
• scientific article; zbMATH DE number 4104204
• Correspondence analysis of incomplete contingency tables
• Correspondence analysis with least absolute residuals
• scientific article; zbMATH DE number 1264698

Cites work

• Assessing brand image through communalities and asymmetries in brand-to-attribute and attribute-to-brand associations
• Correspondence Analysis in Practice
• Correspondence analysis. Theory, practice and new strategies
• scientific article; zbMATH DE number 3466360 (Why is no real title available?)
• scientific article; zbMATH DE number 1416629 (Why is no real title available?)
• Inverse correspondence analysis
• On an eigenvalue property relevant in correspondence analysis and related methods
• Rotation in correspondence analysis

Cited in

(5)

• Inverse correspondence analysis
• Obtaining cell counts for contingency tables from rounded conditional frequencies
• A new mixed integer programming approach for inverse correspondence analysis
• On mathematical optimization for clustering categories in contingency tables
• On the uniqueness of correspondence analysis solutions

This page was built for publication: Retrieving a contingency table from a correspondence analysis solution

Report a bug (only for logged in users!)Click here to report a bug for this page (MaRDI item Q2286973)