I cannot comment on your specific example, because I do not know what it is supposed to communicate.
As with almost any writing device, I think personification is acceptable if:
- it conveys some idea better or more concisely than alternatives,
- the target audience can be expected to understand it,
- there is no loss of precision when it is needed.
Now, the audience of academic writing consists to a considerable extent of non-native speakers, and precision is often paramount. Therefore, the above conditions constrain the use of personifications much stronger than for other types of writing.
Still, there are many cases where a personification is appropriate, for example when you already rigorously defined some concept and now want to explain it by other means. Many such personifications have found their way into scientific terminology or everyday language to the extent that we probably would not even perceive them as personifications anymore. For example, consider the usage of inherit in biology, computer science, and many other contexts. Also, I have used five personifications in this answer so far (mostly unintentionally).
This is from my own academic writing and slightly shortened to reduce context dependence:
These incompatible results show that the model suffers from an inconsistency.
This is a personification:
A scientific model cannot suffer.
If I had been forbidden to use personifications, I would have written something like this instead:
These incompatible results show that the model is inconsistent, which is a considerable problem.
Since I consider this rather clunky, I do not expect anybody to misunderstand my use of suffer, and this is not a matter of definition, I opted for the personification here.
(Now, to some of you “which is a considerable problem” may redundant here, but the paper’s target audience it is not, as evidenced by some of the feedback.)
Again from my own writing and slightly modified:
SymEngine is aspiring to replace the pure Python core of the better-known SymPy.
SymEngine is a software package; it cannot aspire.
Without personification I would have written something like:
SymEngine is developed with the goal that it replaces the pure Python core of the better-known SymPy.
I consider it as likely that somebody stumbles over this more complex sentence structure as over my use of aspire.
For everybody else, the alternative does not add anything.
Again this is a high-level description where precision is not of the essence.