No, don't quit. This is the perfect opportunity to immediately learn a critical way to be happy in your career - develop open communications with your boss. That is the best way to make sure that your roles stay on track with your goals and desires. If you talk, and have a good boss, they will help you out. If you talk and they are unsupportive, then you quit and find a better boss. Choosing your bosses drives much more satisfaction in the long run than almost any other factor of your work.
Could be that your vision and theirs might not be that far apart and you have a new project to tailor your job. But do write it down…
If the job is exactly what you do now and you don’t like it. Then it is time to apply for other positions. From my own experience I know that sticking around will not make you more motivated or happier.
It is okay to switch within 2 months, 6 months or a year.
If it was a bait and switch, just get out. They lied to you, which means they're toxic, and you should just run.
If it was just a miscommunication, then either they're toxic liars who are gaslighting you, or it was just one of those things. But it still isn't going to be what you thought it was, so I'd at least consider finding something better and then walking away from this one.
If it's just temporary, then either they're toxic liars who are just stringing you along, or there's hope. But ask them for when the real thing is going to arrive, and regard that as a deadline. (Don't make it too firm - slippage happens - but if it's a quarter later and nothing has happened, it's probably time to start looking for something else.)
First you have to play with it the way it's being done now.
Research places always have legacy cruft; it's not like they just heard of image processing and want this new thing now.
How I would approach it would be to focus on reproducibility of old results. OK, you have the legacy cruft, you have Python and you have data. Put that together to create a regression test suite which validates that the processing produces certain results.
Once you have that, you can confidently replace legacy parts of it with new stuff, and show, "look, the tests pass; it's handling the existing data in the same way".
They use software and it’s not in great shape. They need someone smart like you to take them from where they are now to a better, more maintainable future!
This incremental evolution of working software to better software is a more realistic task than a greenfield set of tools disconnected from the current workflow/tooling.
You’ll be refactoring working code, making it better, more usable, automating manual tasks, documenting, figuring out how real users can value from incremental improvements, and potentially delivering value rather early.
You will be more effective dev learning to deal with messy, legacy code than one that starts a greenfield project not connected to users existing work.
So many opportunities for leadership and learning!
Why did you have that impression? Was it written down and agreed upon by your employer?
Have you talked to your supervisors?
I would say to get another gig lined up if there's no movement and then renegotiate when you have an offer. Then, of course, give at least two weeks notice.
> I am already graduated though, which makes me a bit nervous
Why does that make you nervous?