ANARC05B - The Double HeLiX


Two finite, strictly increasing, integer sequences are given. Any common integer between the two sequences constitute an intersection point. Take for example the following two sequences where intersection points are
printed in bold:

  • First= 3 5 7 9 20 25 30 40 55 56 57 60 62
  • Second= 1 4 7 11 14 25 44 47 55 57 100

You can ‘walk” over these two sequences in the following way:

  1. You may start at the beginning of any of the two sequences. Now start moving forward.
  2. At each intersection point, you have the choice of either continuing with the same sequence you’re currently on, or switching to the other sequence.

The objective is finding a path that produces the maximum sum of data you walked over. In the above example, the largest possible sum is 450, which is the result of adding 3, 5, 7, 9, 20, 25, 44, 47, 55, 56, 57, 60, and 62

Input

Your program will be tested on a number of test cases. Each test case will be specified on two separate lines. Each line denotes a sequence and is specified using the following format:

n v1 v2 ... vn

Where n is the length of the sequence and vi is the ith element in that sequence. Each sequence will have at least one element but no more than 10,000. All elements are between -10,000 and 10,000 (inclusive).
The last line of the input includes a single zero, which is not part of the test cases.

Output

For each test case, write on a separate line, the largest possible sum that can be produced.

Sample

Input:
13 3 5 7 9 20 25 30 40 55 56 57 60 62
11 1 4 7 11 14 25 44 47 55 57 100
4 -5 100 1000 1005
3 -12 1000 1001
0

Output:
450
2100

hide comments
Rudra Nil Basu: 2016-02-10 17:43:02

Thanks Krishna for the test cases :) Overlooked an important corner case. AC finally :)

Sumit Vohra: 2016-02-08 01:04:46

:) nailed it with dfs O(n + m )

Akshay Damle: 2016-01-28 19:43:21

O(N) solution, AC in 1 go :D
Tested against test cases from spojtoolkit. Some of their test cases are wrong (they don't always have strictly increasing sequences), so be wary of those.

Last edit: 2016-01-28 19:44:50
try2catch: 2016-01-23 09:35:27

simple O(n) greedy approach....single shot AC
why to make it complex using DP?

dokz: 2016-01-18 10:43:59

Getting runtime error, while it works great on my PC and IDEOne.

Last edit: 2016-01-18 10:56:27
nonushikhar: 2016-01-15 13:59:54

O(n) :)

Divyaanand Sinha: 2015-12-23 16:58:09

Used simple greedy approach and binary search to find the common elements but getting TLE..

Last edit: 2015-12-23 17:02:15
sushmitkumar: 2015-12-18 04:04:35

I do not see the use of binary search here.
Is there a solution with better than O(n+m) [where n and m are lengths of the 2 arrays] time complexity?

deerishi: 2015-12-05 05:51:31

Very very simple greedy approach

Anish Kumar: 2015-11-10 19:37:22

Clearly an O(n) solution is possible.


Added by:psetter
Date:2009-07-05
Time limit:1s
Source limit:50000B
Memory limit:1536MB
Cluster: Cube (Intel G860)
Languages:All except: ERL JS-RHINO NODEJS PERL6 VB.NET
Resource:ANARC 2005