@ShoubhikRMaiti , @Tyberius honestly I thought we already had a fortran tag earlier, and I'm surprised we didn't have one until now. I think we should not allow it to be used every time someone has a question about a FORTRAN software (e.g. MOLPRO was written in FORTRAN but questions about MOLPRO should generally go into the molpro tag). However if I'm a developer and want to add a new DFT functional into MOLPRO, I might struggle with FORTRAN errors at compile time,

and the FORTRAN tag would be perfect for that. In the case of the 2 recent questions, certainly the one Tyberius answered with the FORTRAN snippet, would be appropriate for the tag. The other question may have been tagged that way since the user was looking for a FORTRAN code, or a way to process the FORTRAN output.

After a lot of thinking, I've removed the FORTRAN tag from the question about how to post-process that data, because it doesn't have anything to do with FORTRAN.

It's a close call, because he could be a VASP developer that wants to know how to write the FORTRAN code to process that data within VASP, but that wasn't the case here, and he was perfectly happy with the Python solution.

He did use the python tag as well as the FORTRAN one, meaning maybe he wanted either a Python or FORTRAN code, but in this case FORTRAN's not really a very appropriate language to use for the question, so I removed it.

I'm keeping the tag on the other question though!

@NikeDattani I agree with the tag choices for those two questions. The one had enough of a connection to keep the fortran tag, the other didn't. And I agree with the general assessment that a language tag should really only be needed if you are trying to develop or understand code in that language. There's no reason that a question about using (for example) Gaussian would require a fortran tag.

@Tyberius Are you saying you'd like the FORTRAN tag to be added back to the one I removed it from? The question was asking how to post-process some array of numbers. The connection to FORTRAN was that the numbers were the output of VASP, which is a FORTRAN code. Unless I'm a VASP developer working on the post-processing of that data within VASP, so that the users don't have to do it in Python, I don't think FORTRAN is the appropriate language for that post-processing. Python is appropriate.

@NikeDattani No, I was saying I agree with the one where you kept it and the one where you took it off.

@Tyberius ok I thought "tag choices" meant "original tag choices by OP". Now I see that you mean "tag choices made by Nike".