I should write a program for school classification. It should give out all the 5 marks, but nobody can be on the border points or near the border points.
Thanks in advance for your help!

I do not want to write it instead of me, I would like to ask only a good algorithm for this problem.

I would like to ask only a good algorithm for this problem.

Then explain what you don't understand and IN DETAIL explain what you need the program to do.

Then explain what you don't understand and IN DETAIL explain what you need the program to do.

So this program should be a classificator and it should care, that nobody will be dissatisfied. "It should give out all the 5 marks, but nobody can be on the border points or near the border points."

How should I start this program writing?
What is the "motif"?

still too little detail, post how the 5 marks and border points work

There is points given. The program will create points border, with this rules:
- Nobody can be on or near the border points.
- Program should give out all the 5 marks.

still giving too little details for us to work here...

For the 5 marks
what is the start and end of those values?
are they values ranging from 1-n where each mark starts off where the last one ends?
if they are values how will they be given?
can they have overlapping or do each have a unique set of values?

for the border points
are they the values near the start or are they found at the end of each mark,
if so what are the range to tell if the value of the current mark is at the border points

The maximum points are 100, so the points will be 0-100.
The input is the points of the students.

answer the rest of the questions

for the border points
are they the values near the start or are they found at the end of each mark?,
if so what's the range to tell if the value of the current mark is at the border points

for the border points
are they the values near the start or are they found at the end of each mark?,
if so what's the range to tell if the value of the current mark is at the border points

The range will be defined by the points, the rule is that we should give out all the 5 marks.

Repeating your first post does not qualify for explaining IN DETAIL. IN DETAIL means explain every little thing we need to understand the problem.

Repeating your first post does not qualify for explaining IN DETAIL. IN DETAIL means explain every little thing we need to understand the problem.

But what is not undertandable now?

But what is not undertandable now?

What you need to accomplish. What you don't understand. What borders are. Why you need to write this. Why you are so thickheaded. Among other things dealing with this thread.

But what is not undertandable now?

Your leaving too may details here for us to fully comprehend the problem

If I summarize everything you've said all you need to do here is just change the ones who got the border points to a satisfactory grade like everyone who gets a 0 receives a 10 instead and that's that
but I really doubt the program only does this

Sorry this is late, but I haven't used it in a while. If this doesn't help, nothing will:

[boilerplate_help_info]
Posting requests for help must be well thought out if you want help quickly and correctly. Your post did not meet the criteria for quality help. You may get some posts, but are they going to be useful? Check your post with these checkpoints - what is it you missed:

  1. Ask a question that can be answered. Do not ask
    -What's wrong with my code?
    -Why doesn't this work?
    -Anything else that does not give us useful information.
  2. Post your code. If we don't know what you did, how can we possibly help?
    -Use PROPER FORMATTING -- see this
    -Use CODE Tags so your formatting is preserved.
    If we can't follow your code, it's difficult to help. We don't care that you're still working on it. If you want us to read it, it must be readable.
  3. Explain what the code is supposed to do. If we don't know where the target is, how can we help you hit it?
  4. Explain what actually happened! If we don't know where the arrow went when you shot it, how can we tell what went wrong and how far from the target you are?
  5. If you have errors, post them! We can't see your screen. We can't read your mind. You need to tell us what happened.
  6. Do not ask for code. We are not a coding service. We will help you fix your code.
    -If anyone posts working code for you, they are a cheater.
    -If you use that code you are a cheater.
  7. Do not bore us with how new you are. We can tell by your code.
    -Do not apologize. We were all new, and unless you are completely brain dead you will get better.
    -Do not ask us to "take it easy on you."
    -Do not say "I don't know what's going on." That's obvious since you posted for help. Use that time wisely by explaining as best you can so we can help.
  8. Do not apologize for posting 'late'. We don't have any expectations on when you should be posting - 10 minutes or 10 days. We aren't timing your responses.
  9. Do not post your requirements and nothing else. We view that as a lazy do-nothing student that wants us to do their work for them. That's cheating and we will be hard on you.
  10. Do not attach files except when absolutely necessary. Most of us are not going to download files. Add the information to your post.
  11. Do not tell us how urgent it is. Seriously, for us there is no urgency at all. Many that can help will ignore any URGENT or ASAP requests.
  12. Create a good title for your post. The title C++ in the C++ forum is bloody redundant and worthless! What's wrong? equally so. Specifically what are you having trouble with? There is your title. (note: my program is not the answer.)

Think more about your next post so we don't have to play 20 questions to get the info we need to help you.
[/boilerplate_help_info]

This article has been dead for over six months. Start a new discussion instead.