Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge Batch_Karst branch to master #91

Closed
soichih opened this issue Sep 25, 2018 · 5 comments
Closed

Merge Batch_Karst branch to master #91

soichih opened this issue Sep 25, 2018 · 5 comments

Comments

@soichih
Copy link
Contributor

soichih commented Sep 25, 2018

I just realized that we haven't finished merging Batch_Karst branch (that has a MEX files) to master. I am using Batch_Karst branch code for app-life and ideally, I'd like to switch using the master branch instead.

Can we simply do

git checkout master
git merge Batch_Karst

?

@francopestilli
Copy link
Contributor

@soichih yes. Perhaps we can make a release right before we do that?

@soichih
Copy link
Contributor Author

soichih commented Sep 25, 2018

I've created "1.0" branch from master.

Ok, so I am trying to merge Batch_Karst to master. I am seeing following conflict.

@ccaiafa How should I resolve this? Just take what's in Batch_Karst? (use round(nFibers/nBatch)? For MAXMEM calculation, I think we should pick more conservative max (use *1500).

<<<<<<< HEAD
%nNodesMax = round(MAXMEM*30000000/32000000); % In Karst we have available 32,000,000kb of memory, which allows to process up to 30,000,000 nodes;

nNodesMax = round(MAXMEM*15000000/32000000); % 
=======
nNodesMax = round(MAXMEM*30000000/32000000); % In Karst we have available 32,000,000kb of memory, which allows to process up to 30,000,000 nodes;
>>>>>>> origin/Batch_Karst

nTotalNodes = fefgGet(fe.fg,'n total nodes');
nFibers      = feGet(fe,'n fibers');
nBatch = ceil(nTotalNodes/nNodesMax); % Number of batch
<<<<<<< HEAD
nFib_Batch = ceil(nFibers/nBatch); % Number of fibers per batch
=======
nFib_Batch = round(nFibers/nBatch); % Number of fibers per batch
>>>>>>> origin/Batch_Karst


@ccaiafa
Copy link
Collaborator

ccaiafa commented Sep 25, 2018

Hi @soichih, yes to keep batch functionality working you should leave as it is in Batch_Karst branch. Of course you can adjust the use of number of batches depending on the capability of the system where you intend to run ENCODE.
My only concern is that Batch_Karst was designed to run only in Karst (it uses OpenMP implementation) and master is what our paper point out as shared version of ENCODE, i.e. for any platform (not Karst).
Best
Cesar.

@soichih
Copy link
Contributor Author

soichih commented Sep 25, 2018

OK. I've merged it.

I think most computing resources now-a-days have multiple processors. They should all run with openmp code. If this becomes an issue, we should add some if statement inside the code to use non-openmp version of the code; it should not be a separate branch.

Closing this for now.

@soichih soichih closed this as completed Sep 25, 2018
@ccaiafa
Copy link
Collaborator

ccaiafa commented Sep 25, 2018

Sounds good. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants