Thank you for making your AHP software freely available and accessible. I am currently using it for my project and truly appreciate your contribution.
However, I have encountered a couple of issues while using the software:
1.Long sentences for criteria and sub-criteria are not fully displayed in the hierarchy or during pairwise comparisons.
2.Although the decision hierarchy appears correct, when I attempt to complete and submit the pairwise comparisons at level 0, an error message appears: “Hierarchy starts with more than one node – 2 Node.” Additionally, in the input or edit text fields, decimal values appear under each criterion, and there seems to be no option to save the judgments.
I would be very grateful if you could suggest any possible solutions or workarounds for these issues.
The maximal length of criteria text is 60 characters. You need to shorten the names of criteria and sub-criteria. It could be that the error ‘more than one node’ is a consequence of your long wording. Otherwise double-check the hierarchy definition with respect to the names of criteria and sub-criteria, they all have to have a unique name. A sub-criterion must not have the same name as a main criterion.
It took me a while to work out what I was required to do to complete my responses. Better highlighting of what to enter where might help.
Comparing the importance of issues that most likely do not affect each other isn’t as easy as for those that probably do. Just an observation – but you might wish to consider for a comment.
“Control character error, possibly incorrectly encoded”
Dear Sir Klaus,
Thank you very much for making your AHP-OS online tool available, which is very helpful to me as a PhD student. I was exploring your tool, especially the Group Consensus Cluster Analysis. However, I kept getting the error “Control character error, possibly incorrectly encoded.” Any suggestion on how to address this? Thank you.
Dear Mr. Klaus,
Thank you for making your AHP software freely available and accessible. I am currently using it for my project and truly appreciate your contribution.
However, I have encountered a couple of issues while using the software:
1.Long sentences for criteria and sub-criteria are not fully displayed in the hierarchy or during pairwise comparisons.
2.Although the decision hierarchy appears correct, when I attempt to complete and submit the pairwise comparisons at level 0, an error message appears: “Hierarchy starts with more than one node – 2 Node.” Additionally, in the input or edit text fields, decimal values appear under each criterion, and there seems to be no option to save the judgments.
I would be very grateful if you could suggest any possible solutions or workarounds for these issues.
Thank you for your time and support.
The maximal length of criteria text is 60 characters. You need to shorten the names of criteria and sub-criteria. It could be that the error ‘more than one node’ is a consequence of your long wording. Otherwise double-check the hierarchy definition with respect to the names of criteria and sub-criteria, they all have to have a unique name. A sub-criterion must not have the same name as a main criterion.
It took me a while to work out what I was required to do to complete my responses. Better highlighting of what to enter where might help.
Comparing the importance of issues that most likely do not affect each other isn’t as easy as for those that probably do. Just an observation – but you might wish to consider for a comment.
This systemis good ,but it must be supported by good resources in terms of the availability of sustainable energy ,knowledge energy and Skills.
A good reference for survey.
AHP online system is very helpful in decision making…
“Control character error, possibly incorrectly encoded”
Dear Sir Klaus,
Thank you very much for making your AHP-OS online tool available, which is very helpful to me as a PhD student. I was exploring your tool, especially the Group Consensus Cluster Analysis. However, I kept getting the error “Control character error, possibly incorrectly encoded.” Any suggestion on how to address this? Thank you.
All the best,
Alex
Open and then save the json file with a simple text or program editor and select encoding UTF-8.