Too long log on screen when parsing huge amount of data.

[Cloudac7]

As I am manually parsing hundreds of single point calculations, it might cause the log like following:

--- You are parsing data using package Cp2kData ---
Atom names are fake chemical symbols as you set in cp2k input.
--- You are parsing data using package Cp2kData ---
--- You are parsing data using package Cp2kData ---
Atom names are fake chemical symbols as you set in cp2k input.
--- You are parsing data using package Cp2kData ---
--- You are parsing data using package Cp2kData ---
Atom names are fake chemical symbols as you set in cp2k input.
--- You are parsing data using package Cp2kData ---
--- You are parsing data using package Cp2kData ---
Atom names are fake chemical symbols as you set in cp2k input.
--- You are parsing data using package Cp2kData ---
--- You are parsing data using package Cp2kData ---
Atom names are fake chemical symbols as you set in cp2k input.
--- You are parsing data using package Cp2kData ---
--- You are parsing data using package Cp2kData ---
Atom names are fake chemical symbols as you set in cp2k input.
--- You are parsing data using package Cp2kData ---
--- You are parsing data using package Cp2kData ---
Atom names are fake chemical symbols as you set in cp2k input.
--- You are parsing data using package Cp2kData ---
--- You are parsing data using package Cp2kData ---
Atom names are fake chemical symbols as you set in cp2k input.
--- You are parsing data using package Cp2kData ---
--- You are parsing data using package Cp2kData ---
Atom names are fake chemical symbols as you set in cp2k input.
--- You are parsing data using package Cp2kData ---
--- You are parsing data using package Cp2kData ---
Atom names are fake chemical symbols as you set in cp2k input.
--- You are parsing data using package Cp2kData ---
--- You are parsing data using package Cp2kData ---
Atom names are fake chemical symbols as you set in cp2k input.
--- You are parsing data using package Cp2kData ---
--- You are parsing data using package Cp2kData ---
Atom names are fake chemical symbols as you set in cp2k input.
--- You are parsing data using package Cp2kData ---
--- You are parsing data using package Cp2kData ---
Atom names are fake chemical symbols as you set in cp2k input.
--- You are parsing data using package Cp2kData ---
--- You are parsing data using package Cp2kData ---
Atom names are fake chemical symbols as you set in cp2k input.
--- You are parsing data using package Cp2kData ---
--- You are parsing data using package Cp2kData ---
Atom names are fake chemical symbols as you set in cp2k input.
--- You are parsing data using package Cp2kData ---
--- You are parsing data using package Cp2kData ---
Atom names are fake chemical symbols as you set in cp2k input.
--- You are parsing data using package Cp2kData ---
--- You are parsing data using package Cp2kData ---
Atom names are fake chemical symbols as you set in cp2k input.
--- You are parsing data using package Cp2kData ---

It is too long to do any other thing, so it might be a good idea to add a silent mode. And in my opinion, print is not an elegent way to print log in Python, while using logger.info() might be more popular.

So I just submit my concern as an issue.

[robinzyb]

great suggestions. I will refactor print to logger

[robinzyb]

#61
I move these information to debug level. However some warnings are still set at warning level. If you don't want to see them, just set environment variable CP2KDATA_LOG_LEVEL to ERROR or CRITICAL