Development for LHC@home

Now that we are able to control both which applications can be run and how many tasks are assigned per host, is there any need to have both LHC@home and vLHC@home or can we combine them? The main argument for vLHC@home was to not force virtualized tasks onto volunteers. Since we now know how to specify default applications, virtualized applications could be opt-in so we could have the same behaviour in a single project. The advantage would be one username/password etc., a single forum and less confusion.

What is the general consensus?

That's OK for me. I have 2 SixTrack tasks running in this project.
Tullio

I let SixTrack run full utilization and prioritize over other project as it bursty.

if merged would it be more consistent?

As with other project changes I can imagine people would like there credit migrated