[Halld-online] Cleanup of gluon directories

Alexander Somov somov at jlab.org
Tue Feb 18 11:47:24 EST 2014


Hi David,

I propose that you do whatever you need for the monitoring/farms
and we'll take care and finalize dir hierarchy for
electronics initialization. That would be the most efficient way.
Once we come up with the more or less stable conf release,
I'll put it under the svn (coda 3.01 has a lot of new features).

Again, please don't remove/move any of the existing files/dirs
(I already have some bad experience from reorganazing things).

Cheers,
        Alex





On Tue, 18 Feb 2014, David Lawrence wrote:

>
> Hi Alex,
>
>  I appreciate that you’re busy and would like to defer this until later. This is why
> I’ve written so many specifics and have volunteered to do the work. It will clearly
> be easier to finalize the directory structure you want if there is not a lot of junk
> laying around.
>
>  It looks like we’re not actually using /gluex/devel/cool but rather
> /gluex/setups/cool. This indicates it’s either too messy for you to keep
> track of or for me to be able to figure out by looking at the setupcoda3 file.
> Either way, something needs to be done. I’m looking to do this now because it
> is preventing me from effectively working on the things I need to in the
> online system.
>
>  Don’t worry about doing any of the work. I will take care of it and will move files
> into backup areas so nothing will be lost. Once everything is in the repository
> things won’t be so fragile since we’ll have backups and a record or what got
> changed when, why, and by whom. I will likely get started on this Wednesday
> afternoon.
>
> Regards,
> -David
>
> On Feb 18, 2014, at 10:47 AM, Alexander Somov <somov at jlab.org> wrote:
>
>>
>> Hi David,
>>
>> At this stage I would not remove anything. We'll need to finalize
>> the config dir and rol hierarchy and play with hardware setups
>> before we come up with the final dir structure. Currently
>> we are using /gluex/devel and /gluex/release dirs
>>
>> At the moment the cool db (which we and fcal guys are using) is in /gluex/devel/cool
>> Configurations will be redone with the new coda (3.01) release.
>> (we can move the final configuration to either to /gluex/release
>> or /gluex/setups dirs ).
>>
>> Cheers,
>>       Alex
>>
>>
>>
>>
>>
>>
>> On Tue, 18 Feb 2014, David Lawrence wrote:
>>
>>> Hi All,
>>>
>>> I would like to try and clean up the filesystem on the gluon cluster and get some
>>> more files backed up to the repository. This is needed, in part, in order to claim
>>> certain activities as complete. Occasional housekeeping is also just a good idea.
>>>
>>> I don’t want to break any currently working system or anything that is being
>>> actively developed. However, there are lots of scattered bones of previous or
>>> partially developed systems that need to get swept away. Here is a list of
>>> directories that need to be consolidated and/or removed:
>>>
>>> COOL configuration
>>> ——————————————
>>> /gluex/devel/cool
>>> /gluex/devel/cool-old
>>> /gluex/devel/cool_test*
>>> /gluex/setups/cool
>>> /gluex/COOL
>>>
>>> The “cool_test" directory appears to be the one I imported into svn on 2/6/2014 but has
>>> since been renamed. None of the others contain the .svn directory to link back to the
>>> repository. It  looks like from /gluex/setups/setupcoda3 that now /gluex/setups/cool is
>>> being used (unless you are user “somov" in which case /gluonfs1/home/somov/setups/cool
>>> is used).
>>>
>>> I propose that we choose one of these (/gluex/setups/cool) for use in the current
>>> detector-specific DAQ systems and another (/gluex/etc/cool) for development of the
>>> production system. I will use the latter to develop the monitoring system. Both will be
>>> backed up to the svn repository. The others listed above will be removed.
>>>
>>>
>>> ROLs
>>> ——————————————
>>> /gluex/setups/fcal_simple/rol
>>> /gluex/setups/fcal_north/rol
>>> /gluex/setups/fcal_simple_two/rol
>>> /gluex/setups/fcal_n6/rol
>>> /gluex/ROLs
>>> /gluex/builds/devel/packages/rol*
>>> /gluex/release/0.1/src/rol
>>> /gluex/devel/src/rol
>>>
>>> I believe at least a couple of these are in use for various things. The only one connected
>>> to the repository is "/gluex/builds/devel/packages/rol” and I believe it does not contain
>>> any ROLs that are currently (or have ever been) used on a SBC. Regardless, we should
>>> consolidate what we can and then backup everything.
>>>
>>> Based on modification dates, I suspect the following are no longer in use and should be
>>> removed:
>>>
>>> /gluex/setups/fcal_simple/rol
>>> /gluex/setups/fcal_north/rol
>>> /gluex/setups/fcal_simple_two/rol
>>> /gluex/devel/src/rol
>>>
>>> I also propose to consolidate the files in /gluex/ROLs and /gluex/builds/devel/packages/rol
>>> so that they are backed up into the repository. The files in /gluex/setups/fcal_n6/rol
>>> will also be backed up, but to a special directory specific to the FCAL.
>>>
>>>
>>> CODA
>>> ——————————
>>> /gluex/coda
>>> /gluex/devel/coda/
>>> /gluex/old_coda_stuff
>>>
>>> I believe the first one is in use and the other two are no longer in use. I propose we remove
>>> last two.
>>>
>>>
>>> Other duplicates
>>> ——————————————
>>> /gluex/devel
>>> /gluex/builds/devel
>>>
>>> /gluex/setups
>>> /gluex/etc/setups
>>>
>>> It may not be necessary to consolidate either of these, but in general it is confusing for
>>> people to navigate a system where multiple directories have the same name and
>>> overlapping purpose.
>>>
>>>
>>> Please let me know if there are any specific objections to my cleaning things up as described
>>> above. Also, it would be helpful to know if you agree with the changes since I’d like to try moving
>>> on this sometime this week.
>>>
>>> Regards,
>>> -David
>>>
>>>
>>>
>>> _______________________________________________
>>> Halld-online mailing list
>>> Halld-online at jlab.org
>>> https://mailman.jlab.org/mailman/listinfo/halld-online
>
>


More information about the Halld-online mailing list